bgpreport

Network · data from 2026-11-12

AS12946 TeleCable R Cable y Telecable Telecomunicaciones, S.A.U.

Registry name: TeleCable R Cable y Telecable Telecomunicaciones, S.A.U., ES · not in PeeringDB

21IPv4 routes 100.0% RPKI valid · 57.1% with a route object
5IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 14 with no route object for this origin
13Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS12946, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS12946, 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.

93.156.0.0/17 Valid Nonecovered by 93.156.0.0/16 668 99% 67
93.156.128.0/18 Valid Nonecovered by 93.156.0.0/16 668 99% 67
2a00:bec7:10::/48 Valid None 636 100% 67
2a00:bec7:11::/48 Valid None 636 100% 67
2a00:bec7:f800::/40 Valid None 636 100% 67
2a00:bec7:ff00::/40 Valid None 636 100% 67
2a00:bec7::/40 Valid None 605 95% 67
85.152.0.0/17 Valid Nonecovered by 85.152.0.0/16 24 4%low visibility 17
85.152.128.0/17 Valid Nonecovered by 85.152.0.0/16 24 4%low visibility 17
188.171.0.0/17 Valid Nonecovered by 188.171.0.0/16 24 4%low visibility 17
188.171.0.0/20 Valid Nonecovered by 188.171.0.0/16 24 4%low visibility 17
188.171.16.0/20 Valid Nonecovered by 188.171.0.0/16 24 4%low visibility 17
188.171.16.0/21 Valid Nonecovered by 188.171.0.0/16 24 4%low visibility 17
188.171.128.0/17 Valid Nonecovered by 188.171.0.0/16 24 4%low visibility 17
83.97.128.0/17 Valid RIR databaseRIPE 668 99% 67
85.152.0.0/16 Valid RIR databaseRIPE 668 99% 67
185.54.192.0/22 Valid RIR databaseRIPE 668 99% 67
188.171.0.0/16 Valid RIR databaseRIPE 668 99% 67
212.89.0.0/19 Valid RIR databaseRIPE 668 99% 67
213.141.32.0/19 Valid RIR databaseRIPE 668 99% 67
85.152.0.0/19 Valid RIR databaseRIPE 24 4%low visibility 17
85.152.32.0/19 Valid RIR databaseRIPE 24 4%low visibility 17
85.152.64.0/19 Valid RIR databaseRIPE 24 4%low visibility 17
85.152.96.0/19 Valid RIR databaseRIPE 24 4%low visibility 17
212.89.16.0/20 Valid RIR databaseRIPE 24 4%low visibility 17
213.141.32.0/20 Valid RIR databaseRIPE 24 4%low visibility 17

AS-SET

AS12946 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 22 are in fix.csv.

  • Route object: none14
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none93.156.0.0/17No route object for it. A route object for 93.156.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.668 of 673
Route object: none93.156.128.0/18No route object for it. A route object for 93.156.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.668 of 673
Route object: none2a00:bec7:10::/48No route object for it. Add a route object with origin AS12946 in the RIR database for the space.636 of 636
Route object: none2a00:bec7:11::/48No route object for it. Add a route object with origin AS12946 in the RIR database for the space.636 of 636
Route object: none2a00:bec7:f800::/40No route object for it. Add a route object with origin AS12946 in the RIR database for the space.636 of 636
Route object: none2a00:bec7:ff00::/40No route object for it. Add a route object with origin AS12946 in the RIR database for the space.636 of 636
Route object: none2a00:bec7::/40No route object for it. Add a route object with origin AS12946 in the RIR database for the space.605 of 636
Route object: none85.152.0.0/17No route object for it. A route object for 85.152.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none85.152.128.0/17No route object for it. A route object for 85.152.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none188.171.0.0/17No route object for it. A route object for 188.171.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none188.171.0.0/20No route object for it. A route object for 188.171.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none188.171.16.0/20No route object for it. A route object for 188.171.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none188.171.16.0/21No route object for it. A route object for 188.171.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673
Route object: none188.171.128.0/17No route object for it. A route object for 188.171.0.0/16 with origin AS12946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12946 in the RIR database for the space.24 of 673

Route objects not announced

Route objects with origin AS12946 whose prefix no peer sees AS12946 announce. Many are kept on purpose (backup routes, space announced only in some places).

85.152.128.0/19RIPEValid
85.152.160.0/19RIPEValid
85.152.192.0/19RIPEValid
85.152.224.0/19RIPEValid
93.156.0.0/16RIPEValid
212.89.0.0/20RIPEInvalid: maxLength
212.89.1.0/24RIPEValid
212.89.19.0/24RIPEInvalid: 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.