bgpreport

Network · data from 2026-11-12

AS24452 AS-EONFMEDA EonF Meda SL

Registry name: AS-EONFMEDA EonF Meda SL, ES · not in PeeringDB

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

Announced routes

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

213.155.16.0/24 Valid Nonecovered by 213.155.16.0/22 668 99% 67
213.155.17.0/24 Valid Nonecovered by 213.155.16.0/22 668 99% 67
217.179.88.0/24 Valid Nonecovered by 217.179.88.0/22 668 99% 67
217.179.89.0/24 Valid Nonecovered by 217.179.88.0/22 668 99% 67
2a13:8740:1::/48 Valid Nonecovered by 2a13:8740::/29 633 100% 67
2a13:8740::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS24452 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 8 are in fix.csv.

  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none213.155.16.0/24No route object for it. A route object for 213.155.16.0/22 with origin AS24452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24452 in the RIR database for the space.668 of 673
Route object: none213.155.17.0/24No route object for it. A route object for 213.155.16.0/22 with origin AS24452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24452 in the RIR database for the space.668 of 673
Route object: none217.179.88.0/24No route object for it. A route object for 217.179.88.0/22 with origin AS24452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24452 in the RIR database for the space.668 of 673
Route object: none217.179.89.0/24No route object for it. A route object for 217.179.88.0/22 with origin AS24452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24452 in the RIR database for the space.668 of 673
Route object: none2a13:8740:1::/48No route object for it. A route object for 2a13:8740::/29 with origin AS24452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24452 in the RIR database for the space.633 of 636

Route objects not announced

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

213.155.16.0/22RIPEValid
217.179.88.0/22RIPEValid
2a13:8740::/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.