bgpreport

Network · data from 2026-11-12

AS33964 SOGEI-ASN Sogei Societa' Generale d' Informatica S.p.A.

Registry name: SOGEI-ASN Sogei Societa' Generale d' Informatica S.p.A., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33964, 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.
217.175.50.0/24 No ROA Nonecovered by 217.175.48.0/22 673 100% 67
217.175.59.0/24 No ROA Nonecovered by 217.175.48.0/20 672 100% 67
217.175.55.0/24 No ROA RIR databaseRIPE 673 100% 67
217.175.57.0/24 No ROA RIR databaseRIPE 673 100% 67
217.175.48.0/20 No ROA RIR databaseRIPE 672 100% 67
217.175.48.0/22 No ROA RIR databaseRIPE 672 100% 67
217.175.52.0/23 No ROA RIR databaseRIPE 672 100% 67
217.175.54.0/24 No ROA RIR databaseRIPE 672 100% 67
217.175.58.0/24 No ROA RIR databaseRIPE 672 100% 67
217.175.56.0/24 No ROA RIR databaseRIPE 669 99% 67
2a00:e540::/32 Valid None 635 100% 68

AS-SET

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

  • ROA: none10
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none217.175.50.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.673 of 673
Route object: none217.175.50.0/24No route object for it. A route object for 217.175.48.0/22 with origin AS33964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33964 in the RIR database for the space.673 of 673
ROA: none217.175.59.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.672 of 673
Route object: none217.175.59.0/24No route object for it. A route object for 217.175.48.0/20 with origin AS33964 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33964 in the RIR database for the space.672 of 673
ROA: none217.175.55.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.673 of 673
ROA: none217.175.57.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.673 of 673
ROA: none217.175.48.0/20No ROA covers it. Add a ROA for AS33964, maxLength 20.672 of 673
ROA: none217.175.48.0/22No ROA covers it. Add a ROA for AS33964, maxLength 22.672 of 673
ROA: none217.175.52.0/23No ROA covers it. Add a ROA for AS33964, maxLength 23.672 of 673
ROA: none217.175.54.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.672 of 673
ROA: none217.175.58.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.672 of 673
ROA: none217.175.56.0/24No ROA covers it. Add a ROA for AS33964, maxLength 24.669 of 673
Route object: none2a00:e540::/32No route object for it. Add a route object with origin AS33964 in the RIR database for the space.635 of 636

Route objects not announced

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