bgpreport

Network · data from 2026-11-12

AS55061 IEX-MARKET-1 - IEX Group, Inc.

Registry name: IEX-MARKET-1 - IEX Group, Inc., US · not in PeeringDB

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

Announced routes

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

209.51.190.224/28 Invalid: origin None 19 3%low visibility 17
184.105.27.112/29 Invalid: origin None 18 3%low visibility 17
184.105.27.120/29 Invalid: origin None 18 3%low visibility 17
38.133.187.0/24 No ROA None 672 100% 67

AS-SET

AS55061 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 16 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin209.51.190.224/28ROAs covering it name AS6939, not AS55061. If AS55061 should announce it, add a ROA for AS55061.19 of 673
Route object: none209.51.190.224/28No route object for it. Add a route object with origin AS55061 in the RIR database for the space.19 of 673
ROA: origin184.105.27.112/29ROAs covering it name AS6939, not AS55061. If AS55061 should announce it, add a ROA for AS55061.18 of 673
Route object: none184.105.27.112/29No route object for it. Add a route object with origin AS55061 in the RIR database for the space.18 of 673
ROA: origin184.105.27.120/29ROAs covering it name AS6939, not AS55061. If AS55061 should announce it, add a ROA for AS55061.18 of 673
Route object: none184.105.27.120/29No route object for it. Add a route object with origin AS55061 in the RIR database for the space.18 of 673
ROA: none38.133.187.0/24No ROA covers it. Add a ROA for AS55061, maxLength 24.672 of 673
Route object: none38.133.187.0/24No route object for it. Add a route object with origin AS55061 in the RIR database for the space.672 of 673

Route objects not announced

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

23.226.144.0/20ARINNo ROA
136.228.178.0/23ARINNo ROA
136.228.178.0/24ARINNo ROA
136.228.179.0/24ARINNo ROA
162.221.176.0/23ARINNo ROA
172.87.240.0/20ARINNo ROA
198.167.163.0/24ARINNo ROA
2604:1a00:42::/48RADBNo 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.