Network · data from 2026-11-12
AS12334 R Cable y Telecable Telecomunicaciones, S.A.U.
Registry name: R Cable y Telecable Telecomunicaciones, S.A.U., ES · not in PeeringDB
38IPv4 routes
73.7% RPKI valid · 71.1% with a route object
8IPv6 routes
100.0% RPKI valid · 0.0% with a route object
9RPKI invalid
9 origin · 0 maxLength
1No ROA
19 with no route object for this origin
9Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS12334, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS12334, 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.
| 83.97.128.0/17 | Invalid: origin | Other origin only | 2 0%low visibility |
| 85.152.0.0/16 | Invalid: origin | Other origin only | 2 0%low visibility |
| 93.156.0.0/17 | Invalid: origin | None | 2 0%low visibility |
| 93.156.128.0/18 | Invalid: origin | None | 2 0%low visibility |
| 185.54.192.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 188.171.0.0/16 | Invalid: origin | Other origin only | 2 0%low visibility |
| 212.89.0.0/19 | Invalid: origin | Other origin only | 2 0%low visibility |
| 212.89.1.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 213.141.32.0/19 | Invalid: origin | Other origin only | 2 0%low visibility |
| 185.144.232.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 178.60.128.0/18 | Valid | Other origin onlycovered by 178.60.128.0/17 | 671 100% |
| 178.60.192.0/18 | Valid | Other origin onlycovered by 178.60.128.0/17 | 671 100% |
| 2a00:bec0::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:c800::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:d000::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:d800::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:e000::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:e800::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:f000::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 2a00:bec0:f800::/40 | Valid | Nonecovered by 2a00:bec0::/32 | 636 100% |
| 77.26.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.26.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.26.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.26.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.27.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.27.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.27.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 77.27.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 83.165.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 83.165.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 83.165.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 83.165.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.116.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.116.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.116.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.117.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.117.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.117.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.117.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 92.53.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 178.60.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 212.51.32.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 213.60.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 213.60.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 213.60.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 213.60.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS12334 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 33 are in fix.csv.
- ROA: origin9
- ROA: none1
- Route object: none19
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 83.97.128.0/17 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 83.97.128.0/17 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 85.152.0.0/16 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 85.152.0.0/16 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 93.156.0.0/17 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 93.156.0.0/17 | No route object for it. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 93.156.128.0/18 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 93.156.128.0/18 | No route object for it. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 185.54.192.0/22 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 185.54.192.0/22 | Route objects for it name AS12338, AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 188.171.0.0/16 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 188.171.0.0/16 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 212.89.0.0/19 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 212.89.0.0/19 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 212.89.1.0/24 | ROAs covering it name AS12338, AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 212.89.1.0/24 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: origin | 213.141.32.0/19 | ROAs covering it name AS12946, not AS12334. If AS12334 should announce it, add a ROA for AS12334. |
| Route object: none | 213.141.32.0/19 | Route objects for it name AS12946. Add a route object with origin AS12334 in the RIR database for the space. |
| ROA: none | 185.144.232.0/22 | No ROA covers it. Add a ROA for AS12334, maxLength 22. |
| Route object: none | 178.60.128.0/18 | Route objects for it name AS12338. A route object for 178.60.128.0/17 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 178.60.192.0/18 | Route objects for it name AS12338. A route object for 178.60.128.0/17 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:c800::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:d000::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:d800::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:e000::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:e800::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:f000::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
| Route object: none | 2a00:bec0:f800::/40 | No route object for it. A route object for 2a00:bec0::/32 with origin AS12334 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12334 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12334 whose prefix no peer sees AS12334 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.60.128.0/17 | RIPE | No ROA |
| 185.209.60.0/22 | RIPE | No ROA |
| 213.60.0.0/16 | RIPE | Valid |
| 2a00:bec0::/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.