Network · data from 2026-11-12

AS394203 CHICAGOSERVERS - Chicagoservers.org

Registry name: CHICAGOSERVERS - Chicagoservers.org, US · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

5IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No 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 AS394203, seen from no peer

Announced routes

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


208.66.110.0/24	Valid	RIR databaseARIN	672 100%	67
172.99.249.0/24	Valid	RIR databaseARIN	671 100%	68
23.164.52.0/24	Valid	RIR databaseARIN	669 99%	67
208.66.108.0/24	Valid	RIR databaseARIN	668 99%	66
208.66.109.0/24	Valid	RIR databaseARIN	667 99%	67
2602:fed2:7189::/48	Valid	RIR databaseARIN	636 100%	67
2602:fed2:7084::/48	Valid	RIR databaseARIN	635 100%	67
2602:fed2:7110::/48	Valid	RIR databaseARIN	634 100%	69
2602:fed2:7199::/48	Valid	RIR databaseARIN	634 100%	68
2602:fed2:7194::/48	Valid	RIR databaseARIN, RADB	633 100%	69

AS-SET

AS394203 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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