bgpreport

Network · data from 2026-11-12

AS42360 SSP-EUROPE Anexia Cloud Solutions GmbH

Registry name: SSP-EUROPE Anexia Cloud Solutions GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42360, 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.
94.16.4.0/24 No ROA Other origin onlycovered by 94.16.0.0/19 673 100% 66
94.16.0.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.2.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.3.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.7.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.9.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.11.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.20.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.96.0/24 No ROA RIR databaseRIPE 673 100% 66
94.16.6.0/24 Valid RIR databaseRIPE 673 100% 66
94.16.13.0/24 Valid RIR databaseRIPE 673 100% 66
2a00:11c0:77::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: none9
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none94.16.4.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
Route object: none94.16.4.0/24Route objects for it name AS42473. A route object for 94.16.0.0/19 with origin AS42360 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42360 in the RIR database for the space.673 of 673
ROA: none94.16.0.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.2.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.3.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.7.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.9.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.11.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.20.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673
ROA: none94.16.96.0/24No ROA covers it. Add a ROA for AS42360, maxLength 24.673 of 673

Route objects not announced

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

94.16.0.0/19RIPENo 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.