bgpreport

Network · data from 2026-11-12

AS137880 Prime Network

Registry name: PRIME-AS-AP - Prime Network Pvt.ltd, NP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137880, 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.
2406:9cc0:300::/48 Invalid: maxLength Nonecovered by 2406:9cc0::/32 89 14% 41
2406:9cc0:400::/48 Invalid: maxLength Nonecovered by 2406:9cc0::/32 89 14% 41
2406:9cc0:500::/48 Invalid: maxLength Nonecovered by 2406:9cc0::/32 89 14% 41
103.116.48.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.137.10.0/24 No ROA RIR databaseAPNIC 672 100% 66
2001:df5:4300::/48 No ROA RIR databaseAPNIC 636 100% 70
103.157.90.0/23 Valid RIR databaseAPNIC 672 100% 66
103.157.90.0/24 Valid RIR databaseAPNIC 672 100% 66
103.157.91.0/24 Valid RIR databaseAPNIC 672 100% 66
2406:9cc0::/32 Valid RIR databaseAPNIC 636 100% 70
2406:9cc0:5::/48 Valid RIR databaseAPNIC 636 100% 70
2406:9cc0:100::/48 Valid RIR databaseAPNIC 636 100% 70
2406:9cc0:200::/48 Valid RIR databaseAPNIC 636 100% 70
2406:9cc0:fce::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS137880's PeeringDB record names no 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 10 are in fix.csv.

  • ROA: maxLength3
  • ROA: none3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2406:9cc0:300::/48ROA 2406:9cc0::/32 AS137880 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2406:9cc0:300::/48.89 of 636
Route object: none2406:9cc0:300::/48No route object for it. A route object for 2406:9cc0::/32 with origin AS137880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137880 in the RIR database for the space.89 of 636
ROA: maxLength2406:9cc0:400::/48ROA 2406:9cc0::/32 AS137880 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2406:9cc0:400::/48.89 of 636
Route object: none2406:9cc0:400::/48No route object for it. A route object for 2406:9cc0::/32 with origin AS137880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137880 in the RIR database for the space.89 of 636
ROA: maxLength2406:9cc0:500::/48ROA 2406:9cc0::/32 AS137880 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2406:9cc0:500::/48.89 of 636
Route object: none2406:9cc0:500::/48No route object for it. A route object for 2406:9cc0::/32 with origin AS137880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137880 in the RIR database for the space.89 of 636
ROA: none103.116.48.0/24No ROA covers it. Add a ROA for AS137880, maxLength 24.672 of 673
ROA: none103.137.10.0/24No ROA covers it. Add a ROA for AS137880, maxLength 24.672 of 673
ROA: none2001:df5:4300::/48No ROA covers it. Add a ROA for AS137880, maxLength 48.636 of 636

Route objects not announced

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

2406:9cc0:1::/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.