Network · data from 2026-11-12
AS209492 ITSARRIA INFORMATICA Y TELECOMUNICACIONES SARRIA S.L.
Registry name: ITSARRIA INFORMATICA Y TELECOMUNICACIONES SARRIA S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209492, 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.
| 171.22.84.0/23 | Valid | Nonecovered by 171.22.84.0/22 | 672 100% |
| 171.22.86.0/23 | Valid | Nonecovered by 171.22.84.0/22 | 672 100% |
| 171.22.84.0/24 | Valid | Nonecovered by 171.22.84.0/22 | 2 0%low visibility |
| 171.22.85.0/24 | Valid | Nonecovered by 171.22.84.0/22 | 2 0%low visibility |
| 171.22.86.0/24 | Valid | Nonecovered by 171.22.84.0/22 | 2 0%low visibility |
| 171.22.87.0/24 | Valid | Nonecovered by 171.22.84.0/22 | 2 0%low visibility |
| 171.22.84.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.14.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.14.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.15.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.68.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 81.172.60.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 81.172.60.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 81.172.61.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 81.172.62.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 81.172.63.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.163.68.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 212.163.70.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 81.172.62.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS209492 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 12 are in fix.csv.
- Route object: none6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 171.22.84.0/23 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
| Route object: none | 171.22.86.0/23 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
| Route object: none | 171.22.84.0/24 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
| Route object: none | 171.22.85.0/24 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
| Route object: none | 171.22.86.0/24 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
| Route object: none | 171.22.87.0/24 | No route object for it. A route object for 171.22.84.0/22 with origin AS209492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209492 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS209492 whose prefix no peer sees AS209492 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.172.60.0/23 | RIPE | Valid |
| 193.33.40.0/23 | RIPE | Invalid: origin |
| 212.163.68.0/24 | RIPE | Valid |
| 212.163.69.0/24 | RIPE | Valid |
| 212.163.70.0/24 | RIPE | Valid |
| 212.163.71.0/24 | RIPE | Valid |
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.