bgpreport

Network · data from 2026-11-12

AS41986 SARDEGNAIT-AS Sardegna IT srl

Registry name: SARDEGNAIT-AS Sardegna IT srl, IT · not in PeeringDB

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

Announced routes

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

82.85.20.0/24 Invalid: origin None 1 0%low visibility 1
91.213.7.0/24 No ROA None 671 100% 67
195.130.213.0/24 No ROA RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin82.85.20.0/24ROAs covering it name AS8612, not AS41986. If AS41986 should announce it, add a ROA for AS41986.1 of 673
Route object: none82.85.20.0/24No route object for it. Add a route object with origin AS41986 in the RIR database for the space.1 of 673
ROA: none91.213.7.0/24No ROA covers it. Add a ROA for AS41986, maxLength 24.671 of 673
Route object: none91.213.7.0/24No route object for it. Add a route object with origin AS41986 in the RIR database for the space.671 of 673
ROA: none195.130.213.0/24No ROA covers it. Add a ROA for AS41986, maxLength 24.672 of 673

Route objects not announced

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