bgpreport

Network · data from 2026-11-12

AS137273 XNL-AS-AP - X1 NETWORKS (PRIVATE) LIMITED

Registry name: XNL-AS-AP - X1 NETWORKS (PRIVATE) LIMITED, PK · not in PeeringDB

0IPv4 routes
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS137273, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137273, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2402:5a60:1::/48 Valid RIR databaseAPNIC 634 100% 67
2402:5a60::/48 Valid RIR databaseAPNIC 633 100% 67
2402:5a60:2::/48 Valid RIR databaseAPNIC 633 100% 67

AS-SET

AS137273 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

Route objects with origin AS137273 whose prefix no peer sees AS137273 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.106.168.0/22RADBNo ROA
203.55.214.0/23RADBNo ROA
203.55.214.0/24RADBNo ROA
2402:5a60:3::/48APNICValid
2402:5a60:4::/48APNICValid
2402:5a60:5::/48APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.