Hacker News Reader

Comment by hashhar | Hacker News Reader

AWS and GCP are also prone to same kind of data loss if the AZ you are operating in goes down.

They don't automatically geo-replicate things. You still need a backup for the torched EC2 instance to be able to relaunch in another AZ/region.

View on HN

That's true, but it seems whole of SBG region for OVH is within same disaster radius for one fire... with SBG2 destroyed and SBG1 partly damaged.

"The whole site has been isolated, which impacts all our services on SBG1, SBG2, SBG3 and SBG4. "

Wonder if those SBGx were advertised as being the same as "Availability Zones" - when other cloud providers ensure zones are distanced enough from each other (~1km at least) to likely survive events such as fire.

Thats a fair point. If OVH does market them as AZs then it's disingenuous and liable to suits IMO.

No, it isn't, as there's no clear cut definition of what an availability zone is.

The buildings are VERY close to one another.

https://cdn.baxtel.com/data-center/ovh-strasbourg-campus/pho...

That seems, uh, problematic.

Why? They aren't making any sort guarantees with those locations, those aren't advertised as separated fault zones. Those buildings are meant as expansions for existing site.

> but it seems whole of SBG region for OVH is within same disaster radius for one fire

SBG is for Strasbourg. That's not a region. It's a city. Obviously, SBG1 to 4 are in the radius of one fire. It's four different buildings on the same site.

They were not and never advertised as anything similar to AZ. You could not deploy in SBG1,2,3, etc. You only pick city = Strasbourg at deploy time. It's merely a building marker.

Reply on news.ycombinator.com