bgpreport

Network · data from 2026-11-12

AS52317 Internet Winds AG SA

Registry name: AS52317 - Internet Winds AG, AR · PeeringDB

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

Announced routes

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

204.199.4.0/24 No ROA Other IRR onlyRADB 673 100% 66
2803:720::/32 Valid None 633 100% 69
190.112.40.0/23 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.40.0/24 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.41.0/24 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.42.0/23 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.42.0/24 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.43.0/24 Valid Nonecovered by 190.112.40.0/22 4 1%low visibility 3
190.112.40.0/22 Valid Other IRR onlyRADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS52317: AS52317:AS-IWINDS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS52317 isn't in the set, or no route object for AS52317 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS52317 in itNot covered
AS52317:AS-IWINDS In no IRR database read today.

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

  • ROA: none1
  • Route object: none7
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none204.199.4.0/24No ROA covers it. Add a ROA for AS52317, maxLength 24.673 of 673
Route object: RIR204.199.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none2803:720::/32No route object for it. Add a route object with origin AS52317 in the RIR database for the space.633 of 636
Route object: none190.112.40.0/23No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: none190.112.40.0/24No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: none190.112.41.0/24No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: none190.112.42.0/23No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: none190.112.42.0/24No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: none190.112.43.0/24No route object for it. A route object for 190.112.40.0/22 with origin AS52317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52317 in the RIR database for the space.4 of 673
Route object: RIR190.112.40.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: not foundAS52317:AS-IWINDSPeeringDB names AS52317:AS-IWINDS; no IRR database read has it.

Route objects not announced

Every route object with origin AS52317 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.