bgpreport

Network · data from 2026-11-12

AS22208 CTC-AS - Chicago Trading Company

Registry name: CTC-AS - Chicago Trading Company, US · not in PeeringDB

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

Announced routes

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

84.207.243.176/29 Invalid: origin None 2 0%low visibility 2
103.147.252.0/24 No ROA Other origin only 673 100% 67
185.6.131.0/24 No ROA Nonecovered by 185.6.128.0/22 673 100% 67
216.241.75.0/24 No ROA None 673 100% 67
2001:df2:b080::/48 No ROA Other origin only 635 100% 67
216.241.70.0/24 No ROA Other IRR onlyRADB 673 100% 67
2620:126:b000::/40 No ROA Other IRR onlyRADB 633 100% 68
185.6.128.0/24 No ROA RIR databaseRIPE 673 100% 66
2a03:a9a0::/32 No ROA RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none8
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin84.207.243.176/29ROAs covering it name AS13237, not AS22208. If AS22208 should announce it, add a ROA for AS22208.2 of 673
Route object: none84.207.243.176/29No route object for it. Add a route object with origin AS22208 in the RIR database for the space.2 of 673
ROA: none103.147.252.0/24No ROA covers it. Add a ROA for AS22208, maxLength 24.673 of 673
Route object: none103.147.252.0/24Route objects for it name AS139929. Add a route object with origin AS22208 in the RIR database for the space.673 of 673
ROA: none185.6.131.0/24No ROA covers it. Add a ROA for AS22208, maxLength 24.673 of 673
Route object: none185.6.131.0/24No route object for it. A route object for 185.6.128.0/22 with origin AS22208 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22208 in the RIR database for the space.673 of 673
ROA: none216.241.75.0/24No ROA covers it. Add a ROA for AS22208, maxLength 24.673 of 673
Route object: none216.241.75.0/24No route object for it. Add a route object with origin AS22208 in the RIR database for the space.673 of 673
ROA: none2001:df2:b080::/48No ROA covers it. Add a ROA for AS22208, maxLength 48.635 of 636
Route object: none2001:df2:b080::/48Route objects for it name AS139929. Add a route object with origin AS22208 in the RIR database for the space.635 of 636
ROA: none216.241.70.0/24No ROA covers it. Add a ROA for AS22208, maxLength 24.673 of 673
Route object: RIR216.241.70.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2620:126:b000::/40No ROA covers it. Add a ROA for AS22208, maxLength 40.633 of 636
Route object: RIR2620:126:b000::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none185.6.128.0/24No ROA covers it. Add a ROA for AS22208, maxLength 24.673 of 673
ROA: none2a03:a9a0::/32No ROA covers it. Add a ROA for AS22208, maxLength 32.635 of 636

Route objects not announced

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

4.53.100.168/29ARINNo ROA
66.198.48.0/21ALTDB, RADBNo ROA
185.6.128.0/22RIPENo ROA
192.203.228.0/24RADBNo ROA
199.233.217.0/24ALTDBNo ROA
205.215.58.0/24ALTDB, RADBNo ROA
208.49.130.0/24ALTDB, RADBNo ROA
208.116.167.0/24RADBNo ROA

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.