Network · data from 2026-11-12
AS42493 TELELORCA-AS Lorca TV Sol S.L.
Registry name: TELELORCA-AS Lorca TV Sol S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42493, 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.
| 5.35.216.0/24 | Valid | Nonecovered by 5.35.216.0/21 | 673 100% |
| 5.35.217.0/24 | Valid | Nonecovered by 5.35.216.0/21 | 673 100% |
| 2.59.124.0/23 | Valid | Nonecovered by 2.59.124.0/22 | 672 100% |
| 5.35.218.0/23 | Valid | Nonecovered by 5.35.216.0/21 | 672 100% |
| 5.35.220.0/24 | Valid | Nonecovered by 5.35.216.0/21 | 672 100% |
| 5.35.221.0/24 | Valid | Nonecovered by 5.35.216.0/21 | 672 100% |
| 5.35.222.0/24 | Valid | Nonecovered by 5.35.216.0/21 | 672 100% |
| 185.40.149.0/24 | Valid | Nonecovered by 185.40.148.0/22 | 672 100% |
| 185.40.150.0/24 | Valid | Nonecovered by 185.40.148.0/22 | 672 100% |
| 185.40.151.0/24 | Valid | Nonecovered by 185.40.148.0/22 | 672 100% |
| 77.73.40.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.40.148.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2.59.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2.59.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS42493 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 18 are in fix.csv.
- Route object: none10
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.35.216.0/24 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 5.35.217.0/24 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 2.59.124.0/23 | No route object for it. A route object for 2.59.124.0/22 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 5.35.218.0/23 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 5.35.220.0/24 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 5.35.221.0/24 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 5.35.222.0/24 | No route object for it. A route object for 5.35.216.0/21 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 185.40.149.0/24 | No route object for it. A route object for 185.40.148.0/22 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 185.40.150.0/24 | No route object for it. A route object for 185.40.148.0/22 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
| Route object: none | 185.40.151.0/24 | No route object for it. A route object for 185.40.148.0/22 with origin AS42493 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42493 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42493 whose prefix no peer sees AS42493 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.59.124.0/22 | RIPE | Valid |
| 2.59.124.0/24 | RIPE | Valid |
| 2.59.125.0/24 | RIPE | Valid |
| 5.35.216.0/21 | RIPE | Valid |
| 5.35.223.0/24 | RIPE | Valid |
| 77.73.40.0/22 | RIPE | Valid |
| 77.73.44.0/22 | RIPE | Valid |
| 2a01:5780::/32 | 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.