bgpreport

Network · data from 2026-11-12

AS13631 Citadel Investment Group

Registry name: CIG-AS - CITADEL ENTERPRISE AMERICAS LLC, US · PeeringDB

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

Announced routes

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

184.104.200.224/27 Invalid: origin None 18 3%low visibility 17
64.212.61.0/24 No ROA None 673 100% 67
38.57.54.0/24 No ROA None 670 100% 67
216.52.14.0/24 Valid None 667 99% 67
2a13:bb87::/48 Valid Nonecovered by 2a13:bb80::/29 634 100% 72
64.22.160.0/24 Valid RIR databaseARIN 673 100% 70
64.22.161.0/24 Valid RIR databaseARIN, RADB 673 100% 70
64.22.162.0/24 Valid RIR databaseARIN 673 100% 67
64.22.164.0/24 Valid RIR databaseARIN 673 100% 67
64.22.172.0/24 Valid RIR databaseARIN, RADB 673 100% 67
46.255.29.0/24 Valid RIR databaseRIPE 672 100% 70
202.130.214.0/24 Valid RIR databaseAPNIC 671 100% 68
103.187.71.0/24 Valid RIR databaseAPNIC 670 100% 67
194.59.56.0/24 Valid RIR databaseRIPE 670 100% 68
194.59.57.0/24 Valid RIR databaseRIPE 670 100% 68
103.187.70.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
198.22.90.0/24 Valid RIR databaseARIN 664 99% 67

AS-SET

AS13631'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 13 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin184.104.200.224/27ROAs covering it name AS6939, not AS13631. If AS13631 should announce it, add a ROA for AS13631.18 of 673
Route object: none184.104.200.224/27No route object for it. Add a route object with origin AS13631 in the RIR database for the space.18 of 673
ROA: none64.212.61.0/24No ROA covers it. Add a ROA for AS13631, maxLength 24.673 of 673
Route object: none64.212.61.0/24No route object for it. Add a route object with origin AS13631 in the RIR database for the space.673 of 673
ROA: none38.57.54.0/24No ROA covers it. Add a ROA for AS13631, maxLength 24.670 of 673
Route object: none38.57.54.0/24No route object for it. Add a route object with origin AS13631 in the RIR database for the space.670 of 673
Route object: none216.52.14.0/24No route object for it. Add a route object with origin AS13631 in the RIR database for the space.667 of 673
Route object: none2a13:bb87::/48No route object for it. A route object for 2a13:bb80::/29 with origin AS13631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13631 in the RIR database for the space.634 of 636

Route objects not announced

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

64.22.160.0/20ARIN, RADBValid
103.187.70.0/23APNICValid
194.59.56.0/23RIPEValid
2001:470:3d7::/48ARINValid
2a13:bb80::/29RIPEValid

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.