bgpreport

Network · data from 2026-11-12

AS52164 WE-NET

Registry name: WE-NET WE-NET S.r.l., IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52164, 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.
154.60.198.0/23 No ROA None 673 100% 67
130.117.234.0/24 No ROA Other origin only 669 99% 67
154.56.198.0/24 No ROA Other origin only 669 99% 67
154.60.192.0/24 No ROA Other origin only 669 99% 67
154.56.215.0/24 No ROA Other origin only 182 27% 54
193.238.86.0/24 No ROA RIR databaseRIPE 669 99% 67
46.255.30.0/24 No ROA RIR databaseRIPE 668 99% 67
80.244.6.0/24 No ROA RIR databaseRIPE 668 99% 67
2a11:280::/29 No ROA RIR databaseRIPE 602 95% 67

AS-SET

AS52164'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 14 are in fix.csv.

  • ROA: none9
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none154.60.198.0/23No ROA covers it. Add a ROA for AS52164, maxLength 23.673 of 673
Route object: none154.60.198.0/23No route object for it. Add a route object with origin AS52164 in the RIR database for the space.673 of 673
ROA: none130.117.234.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.669 of 673
Route object: none130.117.234.0/24Route objects for it name AS59829. Add a route object with origin AS52164 in the RIR database for the space.669 of 673
ROA: none154.56.198.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.669 of 673
Route object: none154.56.198.0/24Route objects for it name AS59829. Add a route object with origin AS52164 in the RIR database for the space.669 of 673
ROA: none154.60.192.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.669 of 673
Route object: none154.60.192.0/24Route objects for it name AS59829. Add a route object with origin AS52164 in the RIR database for the space.669 of 673
ROA: none154.56.215.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.182 of 673
Route object: none154.56.215.0/24Route objects for it name AS59829. Add a route object with origin AS52164 in the RIR database for the space.182 of 673
ROA: none193.238.86.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.669 of 673
ROA: none46.255.30.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.668 of 673
ROA: none80.244.6.0/24No ROA covers it. Add a ROA for AS52164, maxLength 24.668 of 673
ROA: none2a11:280::/29No ROA covers it. Add a ROA for AS52164, maxLength 29.602 of 636

Route objects not announced

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