bgpreport

Network · data from 2026-11-12

AS396125 CCL Networks

Registry name: CCL-NETWORKS - CCL Networks Inc, CA · PeeringDB

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

Announced routes

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

199.38.236.0/22 No ROA Other IRR onlyRADB 671 100% 68
204.209.29.0/24 No ROA Other IRR onlyRADB 671 100% 68
207.182.0.0/24 No ROA Other IRR onlyRADB 671 100% 68
104.160.232.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
134.195.172.0/22 No ROA RIR databaseARIN 671 100% 68
139.180.28.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
216.73.132.0/22 No ROA RIR databaseARIN 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS396125: AS396125:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS396125 isn't in the set, or no route object for AS396125 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS396125 in itNot covered
AS396125:AS-ALL ARIN 117 Yes 0

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

  • ROA: none7
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none199.38.236.0/22No ROA covers it. Add a ROA for AS396125, maxLength 22.671 of 673
Route object: RIR199.38.236.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.209.29.0/24No ROA covers it. Add a ROA for AS396125, maxLength 24.671 of 673
Route object: RIR204.209.29.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none207.182.0.0/24No ROA covers it. Add a ROA for AS396125, maxLength 24.671 of 673
Route object: RIR207.182.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.160.232.0/22No ROA covers it. Add a ROA for AS396125, maxLength 22.671 of 673
ROA: none134.195.172.0/22No ROA covers it. Add a ROA for AS396125, maxLength 22.671 of 673
ROA: none139.180.28.0/23No ROA covers it. Add a ROA for AS396125, maxLength 23.671 of 673
ROA: none216.73.132.0/22No ROA covers it. Add a ROA for AS396125, maxLength 22.671 of 673

Route objects not announced

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