bgpreport

Network · data from 2026-11-12

AS154701 CDS-AS-AP - Capitalonline Data Service (HK) Co., Limited

Registry name: CDS-AS-AP - Capitalonline Data Service (HK) Co., Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154701, 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.
156.255.7.0/24 Valid Other origin onlycovered by 156.255.6.0/23 2 0%low visibility 2
156.242.83.0/24 Valid Other IRR onlyRADB 672 100% 67
45.196.79.0/24 Valid RIR databaseAFRINIC, RADB 3 0%low visibility 3
45.196.76.0/24 Valid RIR databaseAFRINIC 2 0%low visibility 2
156.255.6.0/23 Valid RIR databaseAFRINIC 2 0%low visibility 2

AS-SET

AS154701 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: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none156.255.7.0/24Route objects for it name AS63199. A route object for 156.255.6.0/23 with origin AS154701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154701 in the RIR database for the space.2 of 673
Route object: RIR156.242.83.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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