Network · data from 2026-11-12

AS50563 ONLYCABLE-AS Onlycable Comunicaciones S.L.

Registry name: ONLYCABLE-AS Onlycable Comunicaciones S.L., ES · not in PeeringDB

51IPv4 routes 100.0% RPKI valid · 98.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

7Route objects not announced registered with origin AS50563, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50563, 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.72.112.0/22	Valid	None	673 100%	67
5.83.64.0/21	Valid	RIR databaseRIPE	673 100%	67
5.83.66.0/23	Valid	RIR databaseRIPE	673 100%	67
5.83.68.0/22	Valid	RIR databaseRIPE	673 100%	67
5.154.0.0/24	Valid	RIR databaseRIPE	673 100%	67
5.154.44.0/24	Valid	RIR databaseRIPE	673 100%	67
37.98.204.0/22	Valid	RIR databaseRIPE	673 100%	67
45.8.76.0/22	Valid	RIR databaseRIPE	673 100%	67
84.236.143.0/24	Valid	RIR databaseRIPE	673 100%	67
85.209.180.0/22	Valid	RIR databaseRIPE	673 100%	67
88.148.52.0/23	Valid	RIR databaseRIPE	673 100%	67
88.148.52.0/24	Valid	RIR databaseRIPE	673 100%	67
89.46.140.0/23	Valid	RIR databaseRIPE	673 100%	67
94.76.146.0/24	Valid	RIR databaseRIPE	673 100%	67
94.76.171.0/24	Valid	RIR databaseRIPE	673 100%	67
152.89.180.0/22	Valid	RIR databaseRIPE	673 100%	67
176.227.145.0/24	Valid	RIR databaseRIPE	673 100%	67
178.156.57.0/24	Valid	RIR databaseRIPE	673 100%	67
178.156.121.0/24	Valid	RIR databaseRIPE	673 100%	67
185.3.116.0/22	Valid	RIR databaseRIPE	673 100%	67
185.27.125.0/24	Valid	RIR databaseRIPE	673 100%	67
185.66.44.0/22	Valid	RIR databaseRIPE	673 100%	67
185.72.112.0/23	Valid	RIR databaseRIPE	673 100%	67
185.72.112.0/24	Valid	RIR databaseRIPE	673 100%	67
185.72.113.0/24	Valid	RIR databaseRIPE	673 100%	67
185.72.114.0/23	Valid	RIR databaseRIPE	673 100%	67
185.72.114.0/24	Valid	RIR databaseRIPE	673 100%	67
185.72.115.0/24	Valid	RIR databaseRIPE	673 100%	67
185.102.210.0/24	Valid	RIR databaseRIPE	673 100%	67
185.125.28.0/22	Valid	RIR databaseRIPE	673 100%	67
195.189.208.0/24	Valid	RIR databaseRIPE	673 100%	67
195.189.209.0/24	Valid	RIR databaseRIPE	673 100%	67
5.83.64.0/24	Valid	RIR databaseRIPE	672 100%	67
5.83.65.0/24	Valid	RIR databaseRIPE	672 100%	67
5.83.95.0/24	Valid	RIR databaseRIPE	672 100%	67
88.148.53.0/24	Valid	RIR databaseRIPE	672 100%	67
93.119.16.0/23	Valid	RIR databaseRIPE	672 100%	67
93.119.16.0/24	Valid	RIR databaseRIPE	672 100%	67
93.119.17.0/24	Valid	RIR databaseRIPE	672 100%	67
93.119.19.0/24	Valid	RIR databaseRIPE	672 100%	67
185.67.106.0/24	Valid	RIR databaseRIPE	672 100%	67
185.67.107.0/24	Valid	RIR databaseRIPE	672 100%	67
188.240.192.0/24	Valid	RIR databaseRIPE	672 100%	67
188.240.193.0/24	Valid	RIR databaseRIPE	672 100%	67
212.85.240.0/23	Valid	RIR databaseRIPE	672 100%	67
212.85.240.0/24	Valid	RIR databaseRIPE	672 100%	67
212.85.241.0/24	Valid	RIR databaseRIPE	672 100%	67
212.85.242.0/23	Valid	RIR databaseRIPE	672 100%	67
212.85.244.0/23	Valid	RIR databaseRIPE	672 100%	67
212.85.244.0/24	Valid	RIR databaseRIPE	672 100%	67
212.85.245.0/24	Valid	RIR databaseRIPE	672 100%	67

AS-SET

AS50563 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 8 are in fix.csv.

Route object: none1
Route object: not announced7

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.72.112.0/22	No route object for it. Add a route object with origin AS50563 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.72.112.0/22

No route object for it. Add a route object with origin AS50563 in the RIR database for the space.

673 of 673

Route objects not announced

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


5.83.95.0/25	RIPE	Invalid: maxLength
5.83.95.128/25	RIPE	Invalid: maxLength
93.119.16.0/22	RIPE	No ROA
94.76.141.0/24	RIPE	Valid
152.89.180.0/23	RIPE	Valid
152.89.182.0/23	RIPE	Valid
2a05:340::/48	RIPE	No ROA

5.83.95.0/25

RIPE

Invalid: maxLength

5.83.95.128/25

RIPE

Invalid: maxLength

93.119.16.0/22

RIPE

No ROA

94.76.141.0/24

RIPE

Valid

152.89.180.0/23

RIPE

Valid

152.89.182.0/23

RIPE

Valid

2a05:340::/48

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.