bgpreport

Network · data from 2026-11-12

AS141006 CT-NEIMENGGU-WULANCHABU-MAN - China Telecom

Registry name: CT-NEIMENGGU-WULANCHABU-MAN - China Telecom, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141006, 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.
1.183.208.0/20 Valid None 672 100% 67
240e:918:a000::/40 Valid None 636 100% 68

AS-SET

AS141006 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 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none1.183.208.0/20No route object for it. Add a route object with origin AS141006 in the RIR database for the space.672 of 673
Route object: none240e:918:a000::/40No route object for it. Add a route object with origin AS141006 in the RIR database for the space.636 of 636

Route objects not announced

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