bgpreport

Network · data from 2026-11-12

AS34731 ARCHIMEDIA-AS Zerouno Informatica S.R.L.

Registry name: ARCHIMEDIA-AS Zerouno Informatica S.R.L., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34731, 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.

88.80.64.0/19 No ROA RIR databaseRIPE 673 100% 67
88.80.64.0/20 No ROA RIR databaseRIPE 673 100% 67
88.80.80.0/20 No ROA RIR databaseRIPE 673 100% 67
80.76.16.0/20 Valid RIR databaseRIPE 673 100% 67
80.76.16.0/21 Valid RIR databaseRIPE 673 100% 67
80.76.24.0/21 Valid RIR databaseRIPE 673 100% 67
80.76.18.0/23 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS34731 isn't in PeeringDB, where networks name their 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 42 are in fix.csv.

  • ROA: none3
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none88.80.64.0/19No ROA covers it. Add a ROA for AS34731, maxLength 19.673 of 673
ROA: none88.80.64.0/20No ROA covers it. Add a ROA for AS34731, maxLength 20.673 of 673
ROA: none88.80.80.0/20No ROA covers it. Add a ROA for AS34731, maxLength 20.673 of 673

Route objects not announced

Route objects with origin AS34731 whose prefix no peer sees AS34731 announce. Many are kept on purpose (backup routes, space announced only in some places).

80.76.16.0/23RIPEValid
80.76.16.0/24RIPEInvalid: maxLength
80.76.17.0/24RIPEInvalid: maxLength
80.76.18.0/24RIPEInvalid: maxLength
80.76.20.0/23RIPEValid
80.76.22.0/23RIPEValid
80.76.24.0/22RIPEValid
80.76.24.0/23RIPEValid
80.76.26.0/23RIPEValid
80.76.28.0/23RIPEValid
80.76.29.0/24RIPEInvalid: maxLength
80.76.30.0/23RIPEValid
80.76.30.0/24RIPEInvalid: maxLength
80.76.31.0/24RIPEInvalid: maxLength
88.80.64.0/23RIPENo ROA
88.80.64.0/24RIPENo ROA
88.80.66.0/23RIPENo ROA
88.80.66.0/24RIPENo ROA
88.80.67.0/24RIPENo ROA
88.80.68.0/23RIPENo ROA
88.80.68.0/24RIPENo ROA
88.80.69.0/24RIPENo ROA
88.80.70.0/23RIPENo ROA
88.80.70.0/24RIPENo ROA
88.80.71.0/24RIPENo ROA
88.80.72.0/23RIPENo ROA
88.80.74.0/23RIPENo ROA
88.80.76.0/23RIPENo ROA
88.80.78.0/23RIPENo ROA
88.80.80.0/21RIPENo ROA
88.80.80.0/23RIPENo ROA
88.80.82.0/23RIPENo ROA
88.80.84.0/23RIPENo ROA
88.80.86.0/23RIPENo ROA
88.80.88.0/22RIPENo ROA
88.80.88.0/23RIPENo ROA
88.80.90.0/23RIPENo ROA
88.80.92.0/23RIPENo ROA
88.80.94.0/23RIPENo ROA

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.