bgpreport

Network · data from 2026-11-12

AS52075 Wifirst

Registry name: WIFIRST Wifirst S.A.S., FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52075, 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.81.196.0/22 Valid RIR databaseRIPE 673 100% 66
46.192.0.0/15 Valid RIR databaseRIPE 673 100% 66
46.193.64.0/19 Valid RIR databaseRIPE 673 100% 66
46.193.96.0/19 Valid RIR databaseRIPE 673 100% 66
46.193.160.0/20 Valid RIR databaseRIPE 673 100% 66
46.193.176.0/20 Valid RIR databaseRIPE 673 100% 66
46.193.208.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.212.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.224.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.228.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.232.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.236.0/22 Valid RIR databaseRIPE 673 100% 66
46.193.240.0/20 Valid RIR databaseRIPE 673 100% 66
193.30.111.0/24 Valid RIR databaseRIPE 673 100% 66
46.193.0.0/19 Valid RIR databaseRIPE 671 100% 66
46.193.32.0/19 Valid RIR databaseRIPE 671 100% 66
46.193.128.0/20 Valid RIR databaseRIPE 671 100% 66
46.193.144.0/20 Valid RIR databaseRIPE 671 100% 66
2a01:7c00:10::/44 Valid RIR databaseRIPE 636 100% 67
2a01:7c01::/42 Valid RIR databaseRIPE 636 100% 67
2a01:7c01:40::/42 Valid RIR databaseRIPE 636 100% 67
2a01:7c00::/29 Valid RIR databaseRIPE 635 100% 67
2a01:7c00:400::/40 Valid RIR databaseRIPE 635 100% 67
2a01:7c00:500::/40 Valid RIR databaseRIPE 635 100% 67
2a01:7c00:600::/40 Valid RIR databaseRIPE 635 100% 67
2a01:7c00:700::/40 Valid RIR databaseRIPE 635 100% 67
2a01:7c01:80::/42 Valid RIR databaseRIPE 635 100% 67
2a01:7c01:c0::/42 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS52075: RIPE::AS52075:AS-GLOBAL. 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 (AS52075 isn't in the set, or no route object for AS52075 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 objectsAS52075 in itNot covered
RIPE::AS52075:AS-GLOBAL RIPE 4159 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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