bgpreport

Network · data from 2026-11-12

AS140105 CMNET-SNIDC-CN-AP - Shaanxi Mobile Communication Company Limited

Registry name: CMNET-SNIDC-CN-AP - Shaanxi Mobile Communication Company Limited, CN · not in PeeringDB

22IPv4 routes 100.0% RPKI valid · 100.0% with a route object
11IPv6 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
12Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS140105, seen from no peer

Announced routes

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

111.19.144.0/24 Valid Other IRR onlyRADB 673 100% 67
111.19.148.0/22 Valid Other IRR onlyRADB 673 100% 67
111.20.240.0/20 Valid Other IRR onlyRADB 673 100% 67
111.20.246.0/24 Valid Other IRR onlyRADB 673 100% 67
111.20.252.0/24 Valid Other IRR onlyRADB 673 100% 67
112.46.48.0/22 Valid Other IRR onlyRADB 673 100% 67
112.46.224.0/21 Valid Other IRR onlyRADB 673 100% 67
120.192.245.0/24 Valid Other IRR onlyRADB 673 100% 67
120.192.246.0/23 Valid Other IRR onlyRADB 673 100% 67
120.192.248.0/23 Valid Other IRR onlyRADB 673 100% 67
120.192.250.0/24 Valid Other IRR onlyRADB 673 100% 67
111.19.144.0/22 Valid Other IRR onlyRADB 82 12% 40
111.19.152.0/23 Valid Other IRR onlyRADB 82 12% 40
111.19.154.0/24 Valid Other IRR onlyRADB 82 12% 40
111.20.4.0/22 Valid Other IRR onlyRADB 82 12% 40
111.20.8.0/22 Valid Other IRR onlyRADB 82 12% 40
111.20.12.0/22 Valid Other IRR onlyRADB 82 12% 40
111.20.19.0/24 Valid Other IRR onlyRADB 82 12% 40
111.20.20.0/22 Valid Other IRR onlyRADB 82 12% 40
111.20.24.0/21 Valid Other IRR onlyRADB 82 12% 40
112.46.0.0/19 Valid Other IRR onlyRADB 82 12% 40
111.20.241.0/24 Valid Other IRR onlyRADB 62 9%low visibility 34
2409:8070:30e8::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30ea::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30eb::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30f8::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30f9::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30fa::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30fb::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8070:30fc::/48 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8c70:3a10::/44 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8c70:3a90::/44 Valid Other IRR onlyRADB 62 10%low visibility 37
2409:8c70:3ab0::/44 Valid Other IRR onlyRADB 62 10%low visibility 37

AS-SET

AS140105 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 33 are in fix.csv.

  • Route object: RIR33
ChangePrefix or setDetailFull-table peers
Route object: RIR111.19.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.19.148.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.20.240.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.20.246.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.20.252.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR112.46.48.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR112.46.224.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.192.245.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.192.246.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.192.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR120.192.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR111.19.144.0/22Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.19.152.0/23Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.19.154.0/24Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.4.0/22Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.8.0/22Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.12.0/22Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.19.0/24Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.20.0/22Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.24.0/21Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR112.46.0.0/19Route object only in RADB. Add it in the RIR database for the space.82 of 673
Route object: RIR111.20.241.0/24Route object only in RADB. Add it in the RIR database for the space.62 of 673
Route object: RIR2409:8070:30e8::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30ea::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30eb::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30f8::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30f9::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30fa::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30fb::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8070:30fc::/48Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8c70:3a10::/44Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8c70:3a90::/44Route object only in RADB. Add it in the RIR database for the space.62 of 636
Route object: RIR2409:8c70:3ab0::/44Route object only in RADB. Add it in the RIR database for the space.62 of 636

Route objects not announced

Every route object with origin AS140105 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.