Network · data from 2026-11-12
AS35130 SFERANET-AS REGISTER S.P.A.
Registry name: SFERANET-AS REGISTER S.P.A., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35130, 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.91.57.0/24 | Valid | Other origin onlycovered by 80.91.56.0/23 | 672 100% |
| 2a02:6000::/33 | Valid | Nonecovered by 2a02:6000::/32 | 636 100% |
| 2a02:6000:ffff::/48 | Valid | Other origin onlycovered by 2a02:6000::/32 | 636 100% |
| 80.91.56.0/24 | Valid | Other origin onlycovered by 80.91.56.0/23 | 156 23% |
| 80.91.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.196.160.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS35130 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 6 are in fix.csv.
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 80.91.57.0/24 | Route objects for it name AS63017. A route object for 80.91.56.0/23 with origin AS35130 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35130 in the RIR database for the space. |
| Route object: none | 2a02:6000::/33 | No route object for it. A route object for 2a02:6000::/32 with origin AS35130 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35130 in the RIR database for the space. |
| Route object: none | 2a02:6000:ffff::/48 | Route objects for it name AS63017. A route object for 2a02:6000::/32 with origin AS35130 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35130 in the RIR database for the space. |
| Route object: none | 80.91.56.0/24 | Route objects for it name AS63017. A route object for 80.91.56.0/23 with origin AS35130 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35130 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35130 whose prefix no peer sees AS35130 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.91.56.0/23 | RIPE | No ROA |
| 2a02:6000::/32 | RIPE | No 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.