bgpreport

Network · data from 2026-11-12

AS149595 Pacelink Network Private Limited

Registry name: PNPL2022-AS-IN - Pacelink Network Private Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149595, 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.
2001:df4:b6c0::/48 No ROA Other IRR onlyRADB 636 100% 70
103.188.236.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.188.237.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
160.250.150.0/24 Valid RIR databaseAPNIC 673 100% 66
160.250.151.0/24 Valid RIR databaseAPNIC 673 100% 66
2001:df1:fd40::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS149595'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 5 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2001:df4:b6c0::/48No ROA covers it. Add a ROA for AS149595, maxLength 48.636 of 636
Route object: RIR2001:df4:b6c0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.188.236.0/23APNIC, RADBValid
160.250.150.0/23APNICValid
2402:6a40:3::c/126APNIC, RADBValid

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.