Network · data from 2026-11-12
AS206077 lecrintv Lecrin Television S.L.
Registry name: lecrintv Lecrin Television S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206077, 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.
| 38.172.193.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 185.196.252.0/23 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 185.196.252.0/24 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 185.196.253.0/24 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 185.196.254.0/23 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 185.196.254.0/24 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 185.196.255.0/24 | Valid | Nonecovered by 185.196.252.0/22 | 673 100% |
| 89.29.250.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.196.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.250.198.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.181.72.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 213.181.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS206077 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 13 are in fix.csv.
- ROA: none1
- Route object: none6
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.172.193.0/24 | No ROA covers it. Add a ROA for AS206077, maxLength 24. |
| Route object: RIR | 38.172.193.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 185.196.252.0/23 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
| Route object: none | 185.196.252.0/24 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
| Route object: none | 185.196.253.0/24 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
| Route object: none | 185.196.254.0/23 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
| Route object: none | 185.196.254.0/24 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
| Route object: none | 185.196.255.0/24 | No route object for it. A route object for 185.196.252.0/22 with origin AS206077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206077 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206077 whose prefix no peer sees AS206077 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.236.245.0/24 | RIPE | Valid |
| 217.26.188.0/23 | RIPE | Valid |
| 217.26.188.0/24 | RIPE | Valid |
| 217.26.189.0/24 | RIPE | Valid |
| 217.76.252.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.