bgpreport

Network · data from 2026-11-12

AS46537 ELMDC - Elm Datacenter LLC

Registry name: ELMDC - Elm Datacenter LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46537, 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.
23.137.64.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.46.236.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.225.53.0/24 No ROA Other IRR onlyRADB 673 100% 67
204.9.88.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.247.109.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS46537 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 41 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none23.137.64.0/24No ROA covers it. Add a ROA for AS46537, maxLength 24.673 of 673
Route object: RIR23.137.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.46.236.0/24No ROA covers it. Add a ROA for AS46537, maxLength 24.673 of 673
Route object: RIR69.46.236.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.225.53.0/24No ROA covers it. Add a ROA for AS46537, maxLength 24.673 of 673
Route object: RIR173.225.53.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.9.88.0/24No ROA covers it. Add a ROA for AS46537, maxLength 24.673 of 673
Route object: RIR204.9.88.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2602:fec4::/36RADBNo ROA
2a05:b900::/32RIPEInvalid: origin
2a05:b901::/32RIPEInvalid: origin
2a05:b902::/32RIPEInvalid: origin
2a05:b903::/32RIPEInvalid: origin
2a05:b904::/32RIPEInvalid: origin
2a05:b905::/32RIPEInvalid: origin
2a05:b906::/32RIPEInvalid: origin
2a05:b907::/32RIPEInvalid: origin
2a09:4500::/32RIPEInvalid: origin
2a09:4501::/32RIPEInvalid: origin
2a09:4502::/32RIPEInvalid: origin
2a09:4503::/32RIPEInvalid: origin
2a09:4504::/32RIPEInvalid: origin
2a09:4505::/32RIPEInvalid: origin
2a09:4506::/32RIPEInvalid: origin
2a09:4507::/32RIPEInvalid: origin
2a09:7500::/32RIPEInvalid: origin
2a09:7501::/32RIPEInvalid: origin
2a09:7502::/32RIPEInvalid: origin
2a09:7503::/32RIPEInvalid: origin
2a09:7504::/32RIPEInvalid: origin
2a09:7505::/32RIPEInvalid: origin
2a09:7506::/32RIPEInvalid: origin
2a09:7507::/32RIPEInvalid: origin
2a13:2ec0::/32RIPENo ROA
2a13:2ec1::/32RIPENo ROA
2a13:2ec2::/32RIPENo ROA
2a13:2ec3::/32RIPENo ROA
2a13:2ec4::/32RIPENo ROA
2a13:2ec5::/32RIPENo ROA
2a13:2ec6::/32RIPENo ROA
2a13:2ec7::/32RIPENo 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.