bgpreport

Network · data from 2026-11-12

AS393362 CDC-01 - Central Dynamics

Registry name: CDC-01 - Central Dynamics, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393362, 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.
198.91.42.0/24 No ROA Nonecovered by 198.91.42.0/23 666 99% 67
198.91.43.0/24 No ROA Nonecovered by 198.91.42.0/23 666 99% 67
198.91.42.0/23 No ROA Other IRR onlyBBOI 672 100% 67
64.135.26.0/24 No ROA Other IRR onlyBBOI 666 99% 67
216.38.164.0/24 No ROA Other IRR onlyBBOI 666 99% 67
8.38.93.0/24 No ROA Other IRR onlyBBOI 658 98% 67

AS-SET

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

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none198.91.42.0/24No ROA covers it. Add a ROA for AS393362, maxLength 24.666 of 673
Route object: none198.91.42.0/24No route object for it. A route object for 198.91.42.0/23 with origin AS393362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393362 in the RIR database for the space.666 of 673
ROA: none198.91.43.0/24No ROA covers it. Add a ROA for AS393362, maxLength 24.666 of 673
Route object: none198.91.43.0/24No route object for it. A route object for 198.91.42.0/23 with origin AS393362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393362 in the RIR database for the space.666 of 673
ROA: none198.91.42.0/23No ROA covers it. Add a ROA for AS393362, maxLength 23.672 of 673
Route object: RIR198.91.42.0/23Route object only in BBOI. Add it in the RIR database for the space.672 of 673
ROA: none64.135.26.0/24No ROA covers it. Add a ROA for AS393362, maxLength 24.666 of 673
Route object: RIR64.135.26.0/24Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none216.38.164.0/24No ROA covers it. Add a ROA for AS393362, maxLength 24.666 of 673
Route object: RIR216.38.164.0/24Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none8.38.93.0/24No ROA covers it. Add a ROA for AS393362, maxLength 24.658 of 673
Route object: RIR8.38.93.0/24Route object only in BBOI. Add it in the RIR database for the space.658 of 673

Route objects not announced

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