Network · data from 2026-11-12
AS210158 madriddigital AGENCIA PARA LA ADMINITRACION DIGITAL DE LA COMUNIDAD DE MADRID
Registry name: madriddigital AGENCIA PARA LA ADMINITRACION DIGITAL DE LA COMUNIDAD DE MADRID, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210158, 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.
| 217.9.24.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 217.9.24.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 217.9.27.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 217.9.24.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 217.9.25.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 217.9.26.0/23 | No ROA | RIR databaseRIPE | 670 100% |
| 217.9.26.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 217.9.26.0/25 | No ROA | RIR databaseRIPE | 21 3%low visibility |
| 217.9.26.128/25 | No ROA | RIR databaseRIPE | 21 3%low visibility |
| 193.36.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.77.128.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 213.0.53.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.77.128.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.77.130.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.235.5.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS210158 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 15 are in fix.csv.
- ROA: none9
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 217.9.24.0/22 | No ROA covers it. Add a ROA for AS210158, maxLength 22. |
| ROA: none | 217.9.24.0/23 | No ROA covers it. Add a ROA for AS210158, maxLength 23. |
| ROA: none | 217.9.27.0/24 | No ROA covers it. Add a ROA for AS210158, maxLength 24. |
| ROA: none | 217.9.24.0/24 | No ROA covers it. Add a ROA for AS210158, maxLength 24. |
| ROA: none | 217.9.25.0/24 | No ROA covers it. Add a ROA for AS210158, maxLength 24. |
| ROA: none | 217.9.26.0/23 | No ROA covers it. Add a ROA for AS210158, maxLength 23. |
| ROA: none | 217.9.26.0/24 | No ROA covers it. Add a ROA for AS210158, maxLength 24. |
| ROA: none | 217.9.26.0/25 | No ROA covers it. Add a ROA for AS210158, maxLength 25. |
| ROA: none | 217.9.26.128/25 | No ROA covers it. Add a ROA for AS210158, maxLength 25. |
Route objects not announced
Route objects with origin AS210158 whose prefix no peer sees AS210158 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.77.128.0/24 | RIPE | Valid |
| 195.77.129.0/24 | RIPE | Valid |
| 195.77.130.0/24 | RIPE | Valid |
| 195.77.131.0/24 | RIPE | Valid |
| 217.9.26.0/26 | RIPE | No ROA |
| 217.9.26.128/26 | 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.