bgpreport

Network · data from 2026-11-12

AS200555 wificanarias WiFi Canarias de Telecomunicaciones y Fibra SL

Registry name: wificanarias WiFi Canarias de Telecomunicaciones y Fibra SL, ES · not in PeeringDB

14IPv4 routes 100.0% RPKI valid · 71.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
35Route objects not announced registered with origin AS200555, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200555, 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.58.208.0/24 Valid Nonecovered by 185.58.208.0/23 672 100% 67
185.58.209.0/24 Valid Nonecovered by 185.58.208.0/23 672 100% 67
185.58.210.0/24 Valid Nonecovered by 185.58.210.0/23 672 100% 67
185.58.211.0/24 Valid Nonecovered by 185.58.210.0/23 672 100% 67
2.58.188.0/22 Valid RIR databaseRIPE 672 100% 67
31.14.60.0/22 Valid RIR databaseRIPE 672 100% 67
89.39.216.0/21 Valid RIR databaseRIPE 672 100% 67
194.146.55.0/24 Valid RIR databaseRIPE 672 100% 67
194.146.63.0/24 Valid RIR databaseRIPE 672 100% 67
194.146.70.0/24 Valid RIR databaseRIPE 672 100% 67
2.58.188.0/24 Valid RIR databaseRIPE 671 100% 67
2.58.189.0/24 Valid RIR databaseRIPE 671 100% 67
2.58.190.0/24 Valid RIR databaseRIPE 671 100% 67
2.58.191.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS200555 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 39 are in fix.csv.

  • Route object: none4
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
Route object: none185.58.208.0/24No route object for it. A route object for 185.58.208.0/23 with origin AS200555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200555 in the RIR database for the space.672 of 673
Route object: none185.58.209.0/24No route object for it. A route object for 185.58.208.0/23 with origin AS200555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200555 in the RIR database for the space.672 of 673
Route object: none185.58.210.0/24No route object for it. A route object for 185.58.210.0/23 with origin AS200555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200555 in the RIR database for the space.672 of 673
Route object: none185.58.211.0/24No route object for it. A route object for 185.58.210.0/23 with origin AS200555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200555 in the RIR database for the space.672 of 673

Route objects not announced

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

31.14.60.0/24RIPEValid
31.14.61.0/24RIPEValid
31.14.62.0/24RIPEValid
31.14.63.0/24RIPEValid
46.24.73.0/24RIPEValid
77.228.196.0/24RIPEValid
77.228.197.0/24RIPEValid
89.39.216.0/22RIPEValid
89.39.216.0/24RIPEValid
89.39.217.0/24RIPEValid
89.39.218.0/24RIPEValid
89.39.219.0/24RIPEValid
89.39.220.0/22RIPEValid
89.39.220.0/24RIPEValid
89.39.221.0/24RIPEValid
89.39.222.0/24RIPEValid
89.39.223.0/24RIPEValid
89.42.120.0/21RIPENo ROA
89.42.120.0/22RIPENo ROA
89.42.120.0/23RIPENo ROA
89.42.122.0/23RIPENo ROA
89.42.122.0/24RIPEInvalid: origin
89.42.123.0/24RIPENo ROA
89.42.124.0/22RIPENo ROA
89.42.124.0/24RIPEInvalid: origin
89.42.125.0/24RIPEInvalid: origin
89.42.126.0/23RIPENo ROA
89.42.126.0/24RIPEInvalid: origin
185.58.208.0/22RIPEValid
185.58.208.0/23RIPEValid
185.58.210.0/23RIPEValid
194.146.99.0/24RIPEValid
212.145.48.0/24RIPEValid
212.145.58.0/24RIPEValid
212.145.62.0/24RIPEValid

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.