bgpreport

Network · data from 2026-11-12

AS58448 AP-CONAC-AS-AP - CONAC (China Organizational Name Administration Center)

Registry name: AP-CONAC-AS-AP - CONAC (China Organizational Name Administration Center), CN · not in PeeringDB

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

Announced routes

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

2401:b400::/48 No ROA Other origin only 629 99% 67
2401:b400:1::/48 No ROA Other origin only 629 99% 67
2401:b400:3::/48 No ROA None 539 85% 67
2401:b400:4::/48 No ROA None 539 85% 67
2401:b400:5::/48 No ROA None 539 85% 67
2401:b400:6::/48 No ROA None 539 85% 67
2401:b400:7::/48 No ROA None 539 85% 67
111.235.160.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
111.235.161.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
111.235.178.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
111.235.179.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
111.235.174.0/24 No ROA Other IRR onlyRADB 411 61% 66
2401:b400:2::/48 No ROA RIR databaseAPNIC 629 99% 67

AS-SET

AS58448 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 26 are in fix.csv.

  • ROA: none13
  • Route object: none7
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2401:b400::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.629 of 636
Route object: none2401:b400::/48Route objects for it name AS58536. Add a route object with origin AS58448 in the RIR database for the space.629 of 636
ROA: none2401:b400:1::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.629 of 636
Route object: none2401:b400:1::/48Route objects for it name AS58536. Add a route object with origin AS58448 in the RIR database for the space.629 of 636
ROA: none2401:b400:3::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.539 of 636
Route object: none2401:b400:3::/48No route object for it. Add a route object with origin AS58448 in the RIR database for the space.539 of 636
ROA: none2401:b400:4::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.539 of 636
Route object: none2401:b400:4::/48No route object for it. Add a route object with origin AS58448 in the RIR database for the space.539 of 636
ROA: none2401:b400:5::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.539 of 636
Route object: none2401:b400:5::/48No route object for it. Add a route object with origin AS58448 in the RIR database for the space.539 of 636
ROA: none2401:b400:6::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.539 of 636
Route object: none2401:b400:6::/48No route object for it. Add a route object with origin AS58448 in the RIR database for the space.539 of 636
ROA: none2401:b400:7::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.539 of 636
Route object: none2401:b400:7::/48No route object for it. Add a route object with origin AS58448 in the RIR database for the space.539 of 636
ROA: none111.235.160.0/24No ROA covers it. Add a ROA for AS58448, maxLength 24.673 of 673
Route object: RIR111.235.160.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none111.235.161.0/24No ROA covers it. Add a ROA for AS58448, maxLength 24.673 of 673
Route object: RIR111.235.161.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none111.235.178.0/24No ROA covers it. Add a ROA for AS58448, maxLength 24.672 of 673
Route object: RIR111.235.178.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none111.235.179.0/24No ROA covers it. Add a ROA for AS58448, maxLength 24.672 of 673
Route object: RIR111.235.179.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none111.235.174.0/24No ROA covers it. Add a ROA for AS58448, maxLength 24.411 of 673
Route object: RIR111.235.174.0/24Route object only in RADB. Add it in the RIR database for the space.411 of 673
ROA: none2401:b400:2::/48No ROA covers it. Add a ROA for AS58448, maxLength 48.629 of 636

Route objects not announced

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

111.235.173.0/24NTTCOM, RADBNo 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.