bgpreport

Network · data from 2026-11-12

AS394230 CDCK

Registry name: CDCK - Civilized Discourse Construction Kit, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394230, 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.
64.71.144.192/27 Invalid: origin None 18 3%low visibility 17
184.104.202.96/27 Invalid: origin None 18 3%low visibility 17
184.105.176.32/27 Invalid: origin None 18 3%low visibility 17
184.105.99.0/24 Valid RIR databaseARIN 673 100% 68
216.66.8.0/24 Valid RIR databaseARIN 673 100% 68
74.82.16.0/24 Valid RIR databaseARIN 670 100% 68
184.104.178.0/24 Valid RIR databaseARIN 670 100% 68
2602:fd3f:1::/48 Valid RIR databaseARIN 635 100% 69
2602:fd3f:2::/48 Valid RIR databaseARIN 635 100% 70
2602:fd3f:3::/48 Valid RIR databaseARIN 635 100% 70
2602:fd3f::/48 Valid RIR databaseARIN 634 100% 69
2602:fd3f:e00::/48 Valid RIR databaseARIN 634 100% 69

AS-SET

AS394230's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: origin3
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin64.71.144.192/27ROAs covering it name AS6939, not AS394230. If AS394230 should announce it, add a ROA for AS394230.18 of 673
Route object: none64.71.144.192/27No route object for it. Add a route object with origin AS394230 in the RIR database for the space.18 of 673
ROA: origin184.104.202.96/27ROAs covering it name AS6939, not AS394230. If AS394230 should announce it, add a ROA for AS394230.18 of 673
Route object: none184.104.202.96/27No route object for it. Add a route object with origin AS394230 in the RIR database for the space.18 of 673
ROA: origin184.105.176.32/27ROAs covering it name AS6939, not AS394230. If AS394230 should announce it, add a ROA for AS394230.18 of 673
Route object: none184.105.176.32/27No route object for it. Add a route object with origin AS394230 in the RIR database for the space.18 of 673

Route objects not announced

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

2001:470:c9::/48ARINValid
2001:470:ca::/48ARINValid

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.