bgpreport

Network · data from 2026-11-12

AS46852 IMC-CHICAGO - IMC Markets

Registry name: IMC-CHICAGO - IMC Markets, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46852, 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.
199.168.44.0/22 No ROA Other IRR onlyNTTCOM 672 100% 67
151.123.169.0/24 Valid RIR databaseARIN 673 100% 66
162.210.153.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS46852 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 5 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none199.168.44.0/22No ROA covers it. Add a ROA for AS46852, maxLength 22.672 of 673
Route object: RIR199.168.44.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

69.25.146.0/24RADBNo ROA
74.217.9.0/24RADBNo ROA
151.123.168.0/24ARINValid

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.