bgpreport

Network · data from 2026-11-12

AS25569 InfoCamere

Registry name: INFOCAMERE-AS InfoCamere SCpA, IT · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
17Route objects not announced registered with origin AS25569, seen from no peer

Announced routes

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

80.82.0.0/20 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS25569'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 17 are in fix.csv.

  • Route object: not announced17

Route objects not announced

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

80.82.0.0/24RIPEValid
80.82.1.0/24RIPEValid
80.82.2.0/24RIPEValid
80.82.3.0/24RIPEValid
80.82.4.0/24RIPEValid
80.82.5.0/24RIPEValid
80.82.6.0/24RIPEValid
80.82.7.0/24RIPEValid
80.82.8.0/24RIPEValid
80.82.9.0/24RIPEValid
80.82.10.0/24RIPEValid
80.82.11.0/24RIPEValid
80.82.12.0/24RIPEValid
80.82.13.0/24RIPEValid
80.82.14.0/24RIPEValid
80.82.15.0/24RIPEValid
2a00:c880::/48RIPENo 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.