bgpreport

Network · data from 2026-11-12

AS18183 NCREE

Registry name: NCREE - National Center for Research on Earthquake Engineering, TW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18183, 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:4500:1100::/40 Valid Nonecovered by 2001:4500::/32 635 100% 70
2001:4500:1100::/41 Valid Nonecovered by 2001:4500::/32 635 100% 70
2001:4500:1180::/41 Valid Nonecovered by 2001:4500::/32 635 100% 70
61.56.8.0/21 Valid Other IRR onlyRADB 673 100% 68
61.56.0.0/20 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
61.56.4.0/24 Valid Other IRR onlyRADB 668 99% 68
202.5.12.0/22 Valid Other IRR onlyNTTCOM, RADB 668 99% 68
2001:4500::/32 Valid Other IRR onlyRADB 635 100% 70
103.189.132.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
2400:85a0::/32 Valid RIR databaseAPNIC, NTTCOM, RADB 635 100% 70

AS-SET

AS18183'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 9 are in fix.csv.

  • Route object: none3
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2001:4500:1100::/40No route object for it. A route object for 2001:4500::/32 with origin AS18183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18183 in the RIR database for the space.635 of 636
Route object: none2001:4500:1100::/41No route object for it. A route object for 2001:4500::/32 with origin AS18183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18183 in the RIR database for the space.635 of 636
Route object: none2001:4500:1180::/41No route object for it. A route object for 2001:4500::/32 with origin AS18183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18183 in the RIR database for the space.635 of 636
Route object: RIR61.56.8.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR61.56.0.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR61.56.4.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR202.5.12.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2001:4500::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

203.5.14.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.