bgpreport

Network · data from 2026-11-12

AS208290 WIFISAX AS208290

Registry name: WIFISAX-NET WIFISAX GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208290, 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.
81.2.187.0/24 Valid Other origin only 17 3%low visibility 14
45.148.208.0/24 Valid RIR databaseRIPE 672 100% 66
45.148.209.0/24 Valid RIR databaseRIPE 672 100% 66
45.148.210.0/24 Valid RIR databaseRIPE 672 100% 66
45.148.211.0/24 Valid RIR databaseRIPE 17 3%low visibility 14

AS-SET

AS208290'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none81.2.187.0/24Route objects for it name AS209784. Add a route object with origin AS208290 in the RIR database for the space.17 of 673

Route objects not announced

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