bgpreport

Network · data from 2026-11-12

AS56910 Digital Realty Greece (56910) - Legacy

Registry name: LamdaHellix Digital Realty Hellas Single Member S.A, GR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56910, 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.
91.241.94.0/23 No ROA Other origin only 671 100% 68
91.216.180.0/24 No ROA RIR databaseRIPE 671 100% 68
185.174.126.0/24 No ROA RIR databaseRIPE 671 100% 68
194.30.178.0/24 No ROA RIR databaseRIPE 671 100% 68
2a04:3e00:1003::/48 Valid Nonecovered by 2a04:3e00::/29 1 0%low visibility 1
31.177.56.0/21 Valid RIR databaseRIPE 671 100% 68
31.177.56.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.57.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.58.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.59.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.60.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.61.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.62.0/24 Valid RIR databaseRIPE 671 100% 68
31.177.63.0/24 Valid RIR databaseRIPE 671 100% 68
86.106.173.0/24 Valid RIR databaseRIPE 671 100% 68
185.4.236.0/24 Valid RIR databaseRIPE 671 100% 68
185.36.232.0/22 Valid RIR databaseRIPE 671 100% 68
185.36.232.0/24 Valid RIR databaseRIPE 671 100% 68
185.36.233.0/24 Valid RIR databaseRIPE 671 100% 68
185.36.234.0/24 Valid RIR databaseRIPE 671 100% 68
185.36.235.0/24 Valid RIR databaseRIPE 671 100% 68
185.109.16.0/22 Valid RIR databaseRIPE 671 100% 68
185.109.16.0/24 Valid RIR databaseRIPE 671 100% 68
185.109.17.0/24 Valid RIR databaseRIPE 671 100% 68
185.109.18.0/24 Valid RIR databaseRIPE 671 100% 68
185.109.19.0/24 Valid RIR databaseRIPE 671 100% 68
188.214.127.0/24 Valid RIR databaseRIPE 671 100% 68
2a04:3e00:1::/48 Valid RIR databaseRIPE 635 100% 69
2a04:3e00::/29 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS56910'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 6 are in fix.csv.

  • ROA: none4
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none91.241.94.0/23No ROA covers it. Add a ROA for AS56910, maxLength 23.671 of 673
Route object: none91.241.94.0/23Route objects for it name AS49582. Add a route object with origin AS56910 in the RIR database for the space.671 of 673
ROA: none91.216.180.0/24No ROA covers it. Add a ROA for AS56910, maxLength 24.671 of 673
ROA: none185.174.126.0/24No ROA covers it. Add a ROA for AS56910, maxLength 24.671 of 673
ROA: none194.30.178.0/24No ROA covers it. Add a ROA for AS56910, maxLength 24.671 of 673
Route object: none2a04:3e00:1003::/48No route object for it. A route object for 2a04:3e00::/29 with origin AS56910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56910 in the RIR database for the space.1 of 636

Route objects not announced

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