bgpreport

Network · data from 2026-11-12

AS146762 SHIXP

Registry name: SHIXP - NATIONAL(SHANGHAI) NEW-TYPE INTERNET EXCHANGE POINT, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS146762, 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.

114.111.185.0/24 Valid Other IRR onlyRADB 673 100% 67
114.111.186.0/24 Valid Other IRR onlyRADB 673 100% 67
114.111.181.0/24 Valid Other IRR onlyRADB 672 100% 66
114.111.182.0/24 Valid Other IRR onlyRADB 672 100% 66
114.111.188.0/24 Valid Other IRR onlyRADB 671 100% 67
114.111.189.0/24 Valid Other IRR onlyRADB 671 100% 67
114.111.180.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
114.111.183.0/24 Valid Other IRR onlyRADB 670 100% 67
114.111.187.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
2400:5f60::/32 Valid Other IRR onlyRADB 454 71% 66
114.111.184.0/24 Valid Other IRR onlyRADB 187 28% 56

AS-SET

AS146762'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 20 are in fix.csv.

  • Route object: RIR11
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: RIR114.111.185.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR114.111.186.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR114.111.181.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.111.182.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.111.188.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR114.111.189.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR114.111.180.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR114.111.183.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR114.111.187.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2400:5f60::/32Route object only in RADB. Add it in the RIR database for the space.454 of 636
Route object: RIR114.111.184.0/24Route object only in RADB. Add it in the RIR database for the space.187 of 673

Route objects not announced

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

103.2.156.0/24RADBValid
103.2.157.0/24RADBValid
103.2.158.0/24RADBValid
103.2.159.0/24RADBValid
114.111.176.0/24RADBValid
114.111.177.0/24RADBValid
114.111.178.0/24RADBValid
114.111.179.0/24RADBValid
114.111.190.0/24RADBValid

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.