bgpreport

Network · data from 2026-11-12

AS47927 Wifiweb srl

Registry name: WIFIWEB WIFIWEB s.r.l., IT · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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 AS47927, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47927, 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.
46.28.120.0/21 Valid RIR databaseRIPE 673 100% 66
94.126.8.0/21 Valid RIR databaseRIPE 673 100% 66
159.255.140.0/22 Valid RIR databaseRIPE 673 100% 66
159.255.152.0/22 Valid RIR databaseRIPE 673 100% 66
178.239.33.0/24 Valid RIR databaseRIPE 673 100% 66
185.63.40.0/22 Valid RIR databaseRIPE 673 100% 66
188.95.72.0/21 Valid RIR databaseRIPE 673 100% 66
2a02:b88::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS47927: AS-WIFIWEB-SET. 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 (AS47927 isn't in the set, or no route object for AS47927 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 objectsAS47927 in itNot covered
AS-WIFIWEB-SET RIPE 7452 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 AS47927 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.