bgpreport

Network · data from 2026-11-12

AS59772 fluidra FLUIDRA SA

Registry name: fluidra FLUIDRA SA, ES · not in PeeringDB

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

Announced routes

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

91.239.209.101/32 Invalid: maxLength None 1 0%low visibility 1
91.239.209.102/32 Invalid: maxLength None 1 0%low visibility 1
91.239.209.128/25 Invalid: maxLength None 1 0%low visibility 1
91.239.209.201/32 Invalid: maxLength None 1 0%low visibility 1
91.239.209.202/32 Invalid: maxLength None 1 0%low visibility 1
91.239.209.0/24 Valid Other origin only 673 100% 67
159.255.150.0/24 Valid Other origin only 673 100% 66

AS-SET

AS59772 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 12 are in fix.csv.

  • ROA: maxLength5
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.239.209.101/32ROA 91.239.209.0/24 AS59772 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.239.209.101/32.1 of 673
Route object: none91.239.209.101/32No route object for it. Add a route object with origin AS59772 in the RIR database for the space.1 of 673
ROA: maxLength91.239.209.102/32ROA 91.239.209.0/24 AS59772 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.239.209.102/32.1 of 673
Route object: none91.239.209.102/32No route object for it. Add a route object with origin AS59772 in the RIR database for the space.1 of 673
ROA: maxLength91.239.209.128/25ROA 91.239.209.0/24 AS59772 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 91.239.209.128/25.1 of 673
Route object: none91.239.209.128/25No route object for it. Add a route object with origin AS59772 in the RIR database for the space.1 of 673
ROA: maxLength91.239.209.201/32ROA 91.239.209.0/24 AS59772 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.239.209.201/32.1 of 673
Route object: none91.239.209.201/32No route object for it. Add a route object with origin AS59772 in the RIR database for the space.1 of 673
ROA: maxLength91.239.209.202/32ROA 91.239.209.0/24 AS59772 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.239.209.202/32.1 of 673
Route object: none91.239.209.202/32No route object for it. Add a route object with origin AS59772 in the RIR database for the space.1 of 673
Route object: none91.239.209.0/24Route objects for it name AS15830. Add a route object with origin AS59772 in the RIR database for the space.673 of 673
Route object: none159.255.150.0/24Route objects for it name AS15830. Add a route object with origin AS59772 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS59772 is announced.

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.