bgpreport

Network · data from 2026-11-12

AS154206 CDN1COM-AS-AP - CDN1.com Limited

Registry name: CDN1COM-AS-AP - CDN1.com Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154206, 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.
101.192.136.0/22 No ROA Other origin only 669 99% 67
101.192.140.0/22 No ROA Other origin only 669 99% 67
101.192.144.0/22 No ROA Other origin only 669 99% 67
101.192.148.0/22 No ROA Other origin only 669 99% 67
101.192.152.0/22 No ROA Other origin only 669 99% 67
101.192.156.0/22 No ROA Other origin only 669 99% 67
45.125.34.0/23 Valid RIR databaseAPNIC, RADB 666 99% 70
45.125.35.0/24 Valid RIR databaseAPNIC 358 53% 64
45.125.34.0/24 Valid RIR databaseAPNIC 65 10%low visibility 39

AS-SET

AS154206 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none101.192.136.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.136.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673
ROA: none101.192.140.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.140.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673
ROA: none101.192.144.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.144.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673
ROA: none101.192.148.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.148.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673
ROA: none101.192.152.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.152.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673
ROA: none101.192.156.0/22No ROA covers it. Add a ROA for AS154206, maxLength 22.669 of 673
Route object: none101.192.156.0/22Route objects for it name AS9305, AS135091, AS150452. Add a route object with origin AS154206 in the RIR database for the space.669 of 673

Route objects not announced

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

156.9.188.0/22ARINValid

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.