Remember the OVHcloud data center fire? Here's why it was so bad (2022)
1–10 of 13 posts
Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#2Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#3Short summary: The building did not have an electrical cutoff mechanism, it lacked an automatic fire extinguisher system, it had wooden ceiling, and two inner courtyards acted as chimneys.
Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#4Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#5I wonder how many of those suing OVH (presumably for lacking due diligence in the DC design) have paid out to their customers for lacking the due diligence to have properly engineered & tested DR plans (off-provider backups etc.).
Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#6Lots of discussion about this then: https://news.ycombinator.com/item?id=30763945
Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#7Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#8Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#9Short summary: The building did not have an electrical cutoff mechanism, it lacked an automatic fire extinguisher system, it had wooden ceiling, and two inner courtyards acted as chimneys.
Sounds like the worst possible setup if you want to avoid a catastrophic loss due to fire.
How did they make out with their insurance?
Re: Remember the OVHcloud data center fire? Here's why it was so bad (2022)
#10It would be interesting to know the DC project author/company name.