bgpreport

Network · data from 2026-11-12

AS142404 China Telecom AS142404

Registry name: CHINANET-AS-AP - China Telecom, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142404, 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.
223.9.192.0/21 Invalid: origin None 125 19% 51
1.71.0.0/21 Valid Other IRR onlyRADB 672 100% 67
1.71.8.0/21 Valid Other IRR onlyRADB 672 100% 67
1.71.80.0/20 Valid Other IRR onlyRADB 672 100% 67
240e:926:3000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:981:8200::/40 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS142404'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 8 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin223.9.192.0/21ROAs covering it name AS4134, not AS142404. If AS142404 should announce it, add a ROA for AS142404.125 of 673
Route object: none223.9.192.0/21No route object for it. Add a route object with origin AS142404 in the RIR database for the space.125 of 673
Route object: RIR1.71.0.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.8.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.80.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:926:3000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:981:8200::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

240e:102:6000::/40RADBNo 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.