bgpreport

Network · data from 2026-11-12

AS17617 NYP-AS-AP - Nanyang Polytechnic

Registry name: NYP-AS-AP - Nanyang Polytechnic, SG · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS17617, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17617, 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.
45.126.60.0/22 No ROA Other IRR onlyRADB 672 100% 67
103.236.196.0/22 No ROA Other IRR onlyRADB 672 100% 67
202.0.127.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.12.94.0/24 No ROA Other IRR onlyRADB 671 100% 67
202.12.95.0/24 No ROA Other IRR onlyRADB 671 100% 67
2401:2f00::/32 No ROA Other IRR onlyRADB 343 54% 63

AS-SET

AS17617 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 15 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.126.60.0/22No ROA covers it. Add a ROA for AS17617, maxLength 22.672 of 673
Route object: RIR45.126.60.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.236.196.0/22No ROA covers it. Add a ROA for AS17617, maxLength 22.672 of 673
Route object: RIR103.236.196.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.0.127.0/24No ROA covers it. Add a ROA for AS17617, maxLength 24.671 of 673
Route object: RIR202.0.127.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.12.94.0/24No ROA covers it. Add a ROA for AS17617, maxLength 24.671 of 673
Route object: RIR202.12.94.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.12.95.0/24No ROA covers it. Add a ROA for AS17617, maxLength 24.671 of 673
Route object: RIR202.12.95.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2401:2f00::/32No ROA covers it. Add a ROA for AS17617, maxLength 32.343 of 636
Route object: RIR2401:2f00::/32Route object only in RADB. Add it in the RIR database for the space.343 of 636

Route objects not announced

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

45.126.60.0/24RADBNo ROA
103.236.196.0/24RADBNo ROA
202.12.94.0/23RADBNo ROA

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.