bgpreport

Network · data from 2026-11-12

AS132573 SAI NGN Network Services

Registry name: SAINGN-AS-IN - SAI NGN Network Services, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132573, 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.
103.17.103.0/24 No ROA Other IRR onlyRADB 672 100% 67
157.119.85.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.17.101.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.17.107.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.17.129.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
115.69.253.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
27.0.48.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
27.0.61.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
27.0.63.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.248.168.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.248.169.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.248.170.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS132573'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 16 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none103.17.103.0/24No ROA covers it. Add a ROA for AS132573, maxLength 24.672 of 673
Route object: RIR103.17.103.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none157.119.85.0/24No ROA covers it. Add a ROA for AS132573, maxLength 24.672 of 673
Route object: RIR157.119.85.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

45.248.168.0/22APNICValid
45.248.168.0/23APNICValid
45.248.170.0/23APNICValid
45.248.171.0/24APNIC, RADBValid
103.17.100.0/23APNICValid
103.17.100.0/24APNICValid
103.17.128.0/22APNICValid
103.17.128.0/23APNICValid
103.17.128.0/24APNICValid
103.17.130.0/23APNICValid
103.17.130.0/24APNICValid
103.17.131.0/24APNICValid

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.