bgpreport

Network · data from 2026-11-12

AS49532 Eonix E.U. Region

Registry name: SERVERHUB-NL Eonix Corporation, US · PeeringDB

18IPv4 routes 88.9% RPKI valid · 94.4% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS49532, seen from no peer

Announced routes

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

50.3.183.0/24 No ROA Nonecovered by 50.3.180.0/22 2 0%low visibility 2
2403:ad80:8002::/48 No ROA None 2 0%low visibility 2
185.137.136.0/22 No ROA Other IRR onlyALTDB, RADB 672 100% 67
2a07:440::/32 No ROA Other IRR onlyRADB 635 100% 67
50.2.36.0/22 Valid RIR databaseARIN 672 100% 67
50.3.70.0/23 Valid RIR databaseARIN 672 100% 67
50.3.72.0/23 Valid RIR databaseARIN 672 100% 67
50.3.76.0/22 Valid RIR databaseARIN 672 100% 67
50.3.80.0/22 Valid RIR databaseARIN 672 100% 67
50.3.84.0/22 Valid RIR databaseARIN 672 100% 67
50.3.164.0/22 Valid RIR databaseARIN 672 100% 67
50.3.196.0/23 Valid RIR databaseARIN 672 100% 67
104.140.188.0/22 Valid RIR databaseARIN 672 100% 67
107.158.94.0/23 Valid RIR databaseARIN 672 100% 67
170.130.172.0/22 Valid RIR databaseARIN, NTTCOM 672 100% 67
173.44.138.0/23 Valid RIR databaseARIN 672 100% 67
173.44.164.0/22 Valid RIR databaseARIN 672 100% 67
173.44.224.0/23 Valid RIR databaseARIN 672 100% 67
173.44.226.0/24 Valid RIR databaseARIN 672 100% 67
173.213.92.0/23 Valid RIR databaseARIN 672 100% 67

AS-SET

AS49532'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 31 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none50.3.183.0/24No ROA covers it. Add a ROA for AS49532, maxLength 24.2 of 673
Route object: none50.3.183.0/24No route object for it. A route object for 50.3.180.0/22 with origin AS49532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49532 in the RIR database for the space.2 of 673
ROA: none2403:ad80:8002::/48No ROA covers it. Add a ROA for AS49532, maxLength 48.2 of 636
Route object: none2403:ad80:8002::/48No route object for it. Add a route object with origin AS49532 in the RIR database for the space.2 of 636
ROA: none185.137.136.0/22No ROA covers it. Add a ROA for AS49532, maxLength 22.672 of 673
Route object: RIR185.137.136.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2a07:440::/32No ROA covers it. Add a ROA for AS49532, maxLength 32.635 of 636
Route object: RIR2a07:440::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

23.90.40.0/22ARINInvalid: origin
23.231.12.0/22ARIN, NTTCOMNo ROA
23.231.16.0/22ARIN, NTTCOMNo ROA
50.3.180.0/22ARINNo ROA
50.3.180.0/23ARINNo ROA
50.3.180.0/24ARINNo ROA
50.3.184.0/22ARINNo ROA
50.3.196.0/22NTTCOMNo ROA
101.99.92.0/24APNICValid
104.140.100.0/22ARIN, NTTCOMNo ROA
104.206.188.0/22ARINInvalid: origin
104.206.240.0/22ARIN, NTTCOMNo ROA
104.206.248.0/22NTTCOMNo ROA
104.206.248.0/23ARINNo ROA
107.158.92.0/22ARIN, NTTCOMNo ROA
107.158.220.0/22NTTCOMNo ROA
173.44.140.0/23ARINInvalid: origin
173.213.106.0/23NTTCOMNo ROA
173.213.122.0/23ARIN, NTTCOMNo ROA
173.213.126.0/23ARINInvalid: origin
173.232.108.0/22NTTCOMNo ROA
173.232.108.0/23ARINInvalid: origin
173.232.194.0/23ARINInvalid: origin

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.