Network · data from 2026-11-12
AS206046 ENAIRE Entidad Publica Empresarial ENAIRE
Registry name: ENAIRE Entidad Publica Empresarial ENAIRE, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206046, 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.
| 185.195.76.0/24 | Valid | Nonecovered by 185.195.76.0/23 | 669 99% |
| 185.195.77.0/24 | Valid | Nonecovered by 185.195.76.0/23 | 669 99% |
| 195.55.44.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS206046 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 7 are in fix.csv.
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.195.76.0/24 | No route object for it. A route object for 185.195.76.0/23 with origin AS206046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206046 in the RIR database for the space. |
| Route object: none | 185.195.77.0/24 | No route object for it. A route object for 185.195.76.0/23 with origin AS206046 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206046 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206046 whose prefix no peer sees AS206046 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.60.162.0/24 | RIPE | Invalid: origin |
| 92.60.163.0/24 | RIPE | Invalid: origin |
| 92.60.165.0/24 | RIPE | Invalid: origin |
| 185.195.76.0/23 | RIPE | No ROA |
| 195.100.28.0/24 | RIPE | Invalid: 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.