Network · data from 2026-11-12
AS197772 NODO50 NODO50, Altavoz por la libertad de expresion y comunicacion
Registry name: NODO50 NODO50, Altavoz por la libertad de expresion y comunicacion, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197772, 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.
| 91.226.176.130/32 | Invalid: maxLength | Nonecovered by 91.226.176.0/24 | 2 0%low visibility |
| 91.226.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS197772 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 4 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 91.226.176.130/32 | ROA 91.226.176.0/24 AS197772 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.226.176.130/32. |
| Route object: none | 91.226.176.130/32 | No route object for it. A route object for 91.226.176.0/24 with origin AS197772 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS197772 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197772 whose prefix no peer sees AS197772 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.226.176.0/23 | RIPE | No ROA |
| 91.226.177.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.