bgpreport

Network · data from 2026-11-12

AS208328 Luigi Labate - L2N.IT

Registry name: L2N Luigi Labate, IT · PeeringDB

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

Announced routes

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

194.56.224.0/24 Invalid: origin Other origin only 2 0%low visibility 2
150.251.130.0/24 No ROA RIR databaseRIPE 673 100% 67
2a0a:6046::/32 Valid None 635 100% 67
85.155.151.0/24 Valid RIR databaseRIPE 673 100% 67
136.148.69.0/24 Valid RIR databaseRIPE 673 100% 67
85.155.148.0/24 Valid RIR databaseRIPE 671 100% 67
2a06:9f42::/32 Valid RIR databaseRIPE 634 100% 67
2a0a:6046:fe00::/40 Valid RIR databaseRIPE 634 100% 67
2a0a:6046:ff00::/40 Valid RIR databaseRIPE 634 100% 67
2a0d:b287:ec00::/40 Valid RIR databaseRIPE 634 100% 67
2a0d:b287:ee00::/40 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS208328: AS208328:AS-LUIGILABATE. 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 (AS208328 isn't in the set, or no route object for AS208328 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 objectsAS208328 in itNot covered
AS208328:AS-LUIGILABATE RIPE 82126 Yes 2

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin194.56.224.0/24ROAs covering it name AS7489, AS218686, not AS208328. If AS208328 should announce it, add a ROA for AS208328.2 of 673
Route object: none194.56.224.0/24Route objects for it name AS218686. Add a route object with origin AS208328 in the RIR database for the space.2 of 673
ROA: none150.251.130.0/24No ROA covers it. Add a ROA for AS208328, maxLength 24.673 of 673
Route object: none2a0a:6046::/32No route object for it. Add a route object with origin AS208328 in the RIR database for the space.635 of 636

Route objects not announced

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

2a0e:97c0:640::/44RIPEValid
2a0e:97c0:640::/48RIPEValid
2a0e:97c0:641::/48RIPEValid
2a0e:97c0:64d::/48RIPEValid
2a0e:b107:21a0::/44RIPENo ROA
2a0e:b107:21a0::/48RIPENo ROA
2a12:bec0:310::/44RIPENo ROA
2a12:bec0:fc0::/42RIPEValid
2a13:9500:4b::/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.