Network · data from 2026-11-12
AS34285 JJAA-AS Sociedad Andaluza para el Desarrollo de las Telecomunicaciones S.A. Medio Propio
Registry name: JJAA-AS Sociedad Andaluza para el Desarrollo de las Telecomunicaciones S.A. Medio Propio, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34285, 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.12.16.0/22 | Valid | Nonecovered by 217.12.16.0/20 | 673 100% |
| 217.12.20.0/24 | Valid | Nonecovered by 217.12.20.0/22 | 669 99% |
| 217.12.21.0/24 | Valid | Nonecovered by 217.12.20.0/22 | 669 99% |
| 217.12.22.0/24 | Valid | Nonecovered by 217.12.20.0/22 | 669 99% |
| 217.12.23.0/24 | Valid | Nonecovered by 217.12.20.0/22 | 669 99% |
| 217.12.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.20.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.197.88.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.197.244.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 217.12.16.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 217.12.16.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.17.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.18.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.24.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.25.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.26.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.27.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.28.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 217.12.28.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS34285 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 8 are in fix.csv.
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.12.16.0/22 | No route object for it. A route object for 217.12.16.0/20 with origin AS34285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34285 in the RIR database for the space. |
| Route object: none | 217.12.20.0/24 | No route object for it. A route object for 217.12.20.0/22 with origin AS34285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34285 in the RIR database for the space. |
| Route object: none | 217.12.21.0/24 | No route object for it. A route object for 217.12.20.0/22 with origin AS34285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34285 in the RIR database for the space. |
| Route object: none | 217.12.22.0/24 | No route object for it. A route object for 217.12.20.0/22 with origin AS34285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34285 in the RIR database for the space. |
| Route object: none | 217.12.23.0/24 | No route object for it. A route object for 217.12.20.0/22 with origin AS34285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34285 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34285 whose prefix no peer sees AS34285 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.197.244.0/23 | RIPE | Invalid: maxLength |
| 185.197.246.0/23 | RIPE | Invalid: maxLength |
| 217.12.24.0/21 | RIPE | Invalid: maxLength |
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.