bgpreport

Network · data from 2026-11-12

AS208288 Woolo Comunicaciones S.L.

Registry name: wiphone Wiphone Telecomunicaciones SL, ES · PeeringDB

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

Announced routes

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

45.147.112.0/23 Valid Nonecovered by 45.147.112.0/22 673 100% 67
45.147.114.0/23 Valid Nonecovered by 45.147.112.0/22 673 100% 67
45.147.112.0/22 Valid RIR databaseRIPE 673 100% 67
45.147.112.0/24 Valid RIR databaseRIPE 672 100% 67
45.147.113.0/24 Valid RIR databaseRIPE 672 100% 67
45.147.114.0/24 Valid RIR databaseRIPE 672 100% 67
45.147.115.0/24 Valid RIR databaseRIPE 672 100% 67
85.255.92.0/22 Valid RIR databaseRIPE 672 100% 67
85.255.92.0/23 Valid RIR databaseRIPE 3 0%low visibility 3
85.255.92.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
85.255.93.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
85.255.94.0/23 Valid RIR databaseRIPE 3 0%low visibility 3
85.255.94.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
85.255.95.0/24 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS208288's PeeringDB record names no 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 9 are in fix.csv.

  • Route object: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none45.147.112.0/23No route object for it. A route object for 45.147.112.0/22 with origin AS208288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208288 in the RIR database for the space.673 of 673
Route object: none45.147.114.0/23No route object for it. A route object for 45.147.112.0/22 with origin AS208288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208288 in the RIR database for the space.673 of 673

Route objects not announced

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

194.34.62.0/23RIPEValid
194.34.62.0/24RIPEValid
194.34.63.0/24RIPEValid
194.34.136.0/23RIPEValid
194.34.136.0/24RIPEValid
194.34.137.0/24RIPEValid
2a0d:2f40::/29RIPENo 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.