Network · data from 2026-11-12
AS51678 IBERMATICA AYESA IBERMATICA, SAU
Registry name: IBERMATICA AYESA IBERMATICA, SAU, ES · not in PeeringDB
26IPv4 routes
100.0% RPKI valid · 42.3% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
15 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS51678, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS51678, 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.
| 5.2.24.0/24 | Valid | Nonecovered by 5.2.24.0/22 | 673 100% |
| 5.2.26.0/24 | Valid | Nonecovered by 5.2.24.0/22 | 673 100% |
| 5.2.27.0/24 | Valid | Nonecovered by 5.2.24.0/22 | 673 100% |
| 5.2.28.0/24 | Valid | Nonecovered by 5.2.28.0/22 | 673 100% |
| 5.2.29.0/24 | Valid | Nonecovered by 5.2.28.0/22 | 673 100% |
| 5.2.30.0/24 | Valid | Nonecovered by 5.2.28.0/22 | 673 100% |
| 5.2.31.0/24 | Valid | Nonecovered by 5.2.28.0/22 | 673 100% |
| 134.255.184.0/24 | Valid | Nonecovered by 134.255.184.0/22 | 673 100% |
| 134.255.185.0/24 | Valid | Nonecovered by 134.255.184.0/22 | 673 100% |
| 134.255.186.0/24 | Valid | Nonecovered by 134.255.184.0/22 | 673 100% |
| 134.255.187.0/24 | Valid | Nonecovered by 134.255.184.0/22 | 673 100% |
| 134.255.188.0/24 | Valid | Nonecovered by 134.255.188.0/22 | 673 100% |
| 134.255.189.0/24 | Valid | Nonecovered by 134.255.188.0/22 | 673 100% |
| 134.255.190.0/24 | Valid | Nonecovered by 134.255.188.0/22 | 673 100% |
| 134.255.191.0/24 | Valid | Nonecovered by 134.255.188.0/22 | 673 100% |
| 46.17.136.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.137.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.138.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.140.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.17.143.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.2.24.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 46.17.136.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 134.255.184.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 2a01:b300::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS51678 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 22 are in fix.csv.
- Route object: none15
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.2.24.0/24 | No route object for it. A route object for 5.2.24.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.26.0/24 | No route object for it. A route object for 5.2.24.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.27.0/24 | No route object for it. A route object for 5.2.24.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.28.0/24 | No route object for it. A route object for 5.2.28.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.29.0/24 | No route object for it. A route object for 5.2.28.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.30.0/24 | No route object for it. A route object for 5.2.28.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 5.2.31.0/24 | No route object for it. A route object for 5.2.28.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.184.0/24 | No route object for it. A route object for 134.255.184.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.185.0/24 | No route object for it. A route object for 134.255.184.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.186.0/24 | No route object for it. A route object for 134.255.184.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.187.0/24 | No route object for it. A route object for 134.255.184.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.188.0/24 | No route object for it. A route object for 134.255.188.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.189.0/24 | No route object for it. A route object for 134.255.188.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.190.0/24 | No route object for it. A route object for 134.255.188.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
| Route object: none | 134.255.191.0/24 | No route object for it. A route object for 134.255.188.0/22 with origin AS51678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51678 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51678 whose prefix no peer sees AS51678 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.2.24.0/22 | RIPE | Valid |
| 5.2.28.0/22 | RIPE | Valid |
| 46.17.136.0/22 | RIPE | Valid |
| 46.17.140.0/22 | RIPE | Valid |
| 134.255.184.0/22 | RIPE | Valid |
| 134.255.188.0/22 | RIPE | Valid |
| 185.92.80.0/22 | RIPE | No 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.