bgpreport

Network · data from 2026-11-12

AS140707 UNICOM-NXZW-IDC - UNICOM Ningxia province network

Registry name: UNICOM-NXZW-IDC - UNICOM Ningxia province network, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140707, 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.
116.172.74.0/24 Valid Nonecovered by 116.172.72.0/22 673 100% 67
116.172.64.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.68.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.72.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.72.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.73.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.75.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.76.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.80.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.84.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.84.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.86.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.87.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.88.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.88.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.90.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.91.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.92.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.92.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.93.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.94.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.96.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.96.0/24 Valid Other IRR onlyRADB 673 100% 67
116.172.100.0/22 Valid Other IRR onlyRADB 673 100% 67
116.172.89.0/24 Valid Other IRR onlyRADB 670 100% 67
2408:81a3:c800::/48 Valid RIR databaseAPNIC 629 99% 67
2408:81a3:ca66::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c000::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c001::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c002::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c003::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c004::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c005::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c006::/48 Valid RIR databaseAPNIC 629 99% 67
2408:8779:c007::/48 Valid RIR databaseAPNIC 629 99% 67

AS-SET

AS140707 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 25 are in fix.csv.

  • Route object: none1
  • Route object: RIR24
ChangePrefix or setDetailFull-table peers
Route object: none116.172.74.0/24No route object for it. A route object for 116.172.72.0/22 with origin AS140707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140707 in the RIR database for the space.673 of 673
Route object: RIR116.172.64.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.68.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.72.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.72.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.75.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.76.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.80.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.84.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.84.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.86.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.87.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.88.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.88.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.90.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.91.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.92.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.92.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.93.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.94.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.96.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.96.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.100.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.172.89.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS140707 is announced.

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.