bgpreport

Network · data from 2026-11-12

AS8265 Fastnet Italy

Registry name: FASTNET-BKB-ASN FASTNET S.R.L., IT · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
44Route objects not announced registered with origin AS8265, seen from no peer

Announced routes

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

195.96.192.0/19 Valid RIR databaseRIPE 672 100% 67
185.28.52.0/22 Valid RIR databaseRIPE 670 100% 67
2a02:2888::/32 Valid RIR databaseRIPE 635 100% 67
2a02:2888::/33 Valid RIR databaseRIPE 635 100% 67
2a02:2888:8000::/33 Valid RIR databaseRIPE 635 100% 67
195.96.192.0/20 Valid RIR databaseRIPE 233 35% 55
195.96.208.0/20 Valid RIR databaseRIPE 233 35% 55
185.28.52.0/23 Valid RIR databaseRIPE 231 34% 55
185.28.54.0/23 Valid RIR databaseRIPE 231 34% 55

AS-SET

PeeringDB's irr_as_set for AS8265: RIPE::AS-FASTN. 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 (AS8265 isn't in the set, or no route object for AS8265 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 objectsAS8265 in itNot covered
RIPE::AS-FASTN RIPE 2173 Yes 0

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 44 are in fix.csv.

  • Route object: not announced44

Route objects not announced

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

185.28.52.0/24RIPEValid
185.28.53.0/24RIPEValid
185.28.54.0/24RIPEValid
185.28.55.0/24RIPEValid
195.96.192.0/24RIPEValid
195.96.193.0/24RIPEValid
195.96.194.0/23RIPEValid
195.96.194.0/24RIPEValid
195.96.195.0/24RIPEValid
195.96.196.0/22RIPEValid
195.96.196.0/24RIPEValid
195.96.197.0/24RIPEValid
195.96.198.0/24RIPEValid
195.96.199.0/24RIPEValid
195.96.200.0/22RIPEValid
195.96.200.0/24RIPEValid
195.96.201.0/24RIPEValid
195.96.202.0/24RIPEValid
195.96.203.0/24RIPEValid
195.96.204.0/22RIPEValid
195.96.204.0/24RIPEValid
195.96.205.0/24RIPEValid
195.96.206.0/24RIPEValid
195.96.207.0/24RIPEValid
195.96.208.0/21RIPEValid
195.96.208.0/24RIPEValid
195.96.209.0/24RIPEValid
195.96.210.0/24RIPEValid
195.96.211.0/24RIPEValid
195.96.212.0/24RIPEValid
195.96.213.0/24RIPEValid
195.96.214.0/24RIPEValid
195.96.215.0/24RIPEValid
195.96.216.0/21RIPEValid
195.96.216.0/24RIPEValid
195.96.217.0/24RIPEValid
195.96.218.0/24RIPEValid
195.96.219.0/24RIPEValid
195.96.220.0/22RIPEValid
195.96.220.0/24RIPEValid
195.96.221.0/24RIPEValid
195.96.222.0/24RIPEValid
195.96.223.0/24RIPEValid
2a02:2888:8265::/48RIPEValid

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.