bgpreport

Network · data from 2026-11-12

AS207028 Senza Fili Senza Confini

Registry name: SFSC ASSOCIAZIONE DI PROMOZIONE SOCIALE SENZA FILI SENZA CONFINI, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207028, 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.
2a0a:1302::/32 No ROA RIR databaseRIPE 636 100% 67
2a0a:1303::/32 No ROA RIR databaseRIPE 636 100% 67
185.168.96.0/24 Valid RIR databaseRIPE 671 100% 66
185.168.97.0/24 Valid RIR databaseRIPE 671 100% 66
185.168.98.0/24 Valid RIR databaseRIPE 671 100% 66
185.168.99.0/24 Valid RIR databaseRIPE 671 100% 66
2a0a:1300::/32 Valid RIR databaseRIPE 636 100% 67
2a0a:1301::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS207028'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 4 are in fix.csv.

  • ROA: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:1302::/32No ROA covers it. Add a ROA for AS207028, maxLength 32.636 of 636
ROA: none2a0a:1303::/32No ROA covers it. Add a ROA for AS207028, maxLength 32.636 of 636

Route objects not announced

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

2a0a:1304::/32RIPENo ROA
2a0a:1304::1/128RIPENo 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.