bgpreport

Network · data from 2026-11-12

AS207029 Wime

Registry name: WiMe-AS Wime Srl, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207029, 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.85.24.0/22 Valid RIR databaseRIPE 673 100% 67
185.134.8.0/22 Valid RIR databaseRIPE 673 100% 67
185.210.112.0/22 Valid RIR databaseRIPE 673 100% 67
213.226.104.0/22 Valid RIR databaseRIPE 673 100% 67
185.85.20.0/24 Valid RIR databaseRIPE 670 100% 67
185.85.24.0/23 Valid RIR databaseRIPE 670 100% 67
185.85.26.0/23 Valid RIR databaseRIPE 670 100% 67
185.134.8.0/23 Valid RIR databaseRIPE 670 100% 67
185.134.10.0/23 Valid RIR databaseRIPE 670 100% 67
185.210.112.0/23 Valid RIR databaseRIPE 670 100% 67
185.210.114.0/23 Valid RIR databaseRIPE 670 100% 67
213.226.104.0/23 Valid RIR databaseRIPE 670 100% 67
213.226.106.0/23 Valid RIR databaseRIPE 670 100% 67
2a05:a580::/29 Valid RIR databaseRIPE 635 100% 67
2a06:ea00::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS207029: AS207029:AS-WIME-SRL. 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 (AS207029 isn't in the set, or no route object for AS207029 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 objectsAS207029 in itNot covered
AS207029:AS-WIME-SRL RIPE 010 No 15

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.

  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS207029:AS-WIME-SRLAS207029 isn't in AS207029:AS-WIME-SRL (RIPE) once expanded. Add AS207029 to it.

Route objects not announced

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