bgpreport

Network · data from 2026-11-12

AS202421 Wimaz

Registry name: wimaz Wimaz S. L., ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202421, 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.204.176.0/23 Valid Nonecovered by 185.204.176.0/22 673 100% 67
185.204.178.0/23 Valid Nonecovered by 185.204.176.0/22 673 100% 67
103.229.169.0/24 Valid RIR databaseRIPE 673 100% 67
185.85.254.0/24 Valid RIR databaseRIPE 673 100% 67
185.204.176.0/22 Valid RIR databaseRIPE 673 100% 67
185.204.176.0/24 Valid RIR databaseRIPE 673 100% 67
185.204.177.0/24 Valid RIR databaseRIPE 673 100% 67
185.204.178.0/24 Valid RIR databaseRIPE 673 100% 67
185.204.179.0/24 Valid RIR databaseRIPE 673 100% 67
2a0a:fac0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS202421'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 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none185.204.176.0/23No route object for it. A route object for 185.204.176.0/22 with origin AS202421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202421 in the RIR database for the space.673 of 673
Route object: none185.204.178.0/23No route object for it. A route object for 185.204.176.0/22 with origin AS202421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202421 in the RIR database for the space.673 of 673

Route objects not announced

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