Network · data from 2026-11-12
AS201343 VALENCIACABLE ONLYCABLE FIBRA SL
Registry name: VALENCIACABLE ONLYCABLE FIBRA SL, ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201343, 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.
| 185.102.211.0/24 | Valid | Nonecovered by 185.102.208.0/22 | 672 100% |
| 89.46.136.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.67.208.0/23 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS201343 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.102.211.0/24 | No route object for it. A route object for 185.102.208.0/22 with origin AS201343 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201343 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201343 whose prefix no peer sees AS201343 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.102.208.0/22 | RIPE | No ROA |
| 185.102.211.0/25 | RIPE | Invalid: maxLength |
| 185.102.211.128/26 | RIPE | Invalid: maxLength |
| 185.102.211.192/26 | 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.