Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OVH Incident in Strasbourg

status.ovh.com

Post reply on HN
Print view View original

131–140 of 207 posts

Re: OVH Incident in Strasbourg

#131

Post by r1ch »

tyingq wrote: post #109
vabene1111 wrote: post #52

Earlier quoted context omitted.

its OVH: The Hardware is good DDoS protection is good The Prices are high but support/administration does not work well, i have a lot of really weird story's with them, from them plugging in a keyboard in our server to reboot it (without any reason) to taking down a server for a requested maintenance only to notice after 4 hours of downtime that they did not ask their bosses if they were allowed to even perform the m…

>ts OVH: The Hardware is good DDoS protection is good The Prices are high The prices are high? Compared to what? Cheap is their raison d'être.

Their prices are pretty amazing for some of the configurations you can put together, especially since you can pay a large setup fee in exchange for a lower monthly rate.

Just the bandwidth alone would cost us 3x what we pay at OVH if we were with one of the big cloud providers.

Re: OVH Incident in Strasbourg

#132

Post by r1ch »

PuffinBlue wrote: post #51
therealmarv wrote: post #21

wow, yesterday I was playing with their public cloud because considering choosing them. I had some connection problem with my private networking there (deleted it more than once) and opened a ticket. If it was me... sorry, haha. Not good advertisement but it can happen to everyone.

Huh, I was just looking at them too. Contrary to popular opinion, I kinda prefer it when these things happen before I sign up so that in the post-mortem usually whatever architectural failure lead to the outage is corrected and you get a stronger service. Usually.

OVH are very open about their outages and root causes. Even routine maintenance tasks are cataloged with updates at http://status.ovh.net

As a more technical user it's nice to have providers that give this information rather than the boilerplate "Issue with an upstream provider" over and over.

Re: OVH Incident in Strasbourg

#133

Post by HelloNurse »

chii wrote: post #128
contingencies wrote: post #79

To make error is human. To propagate error to all server in automatic way is #devops. - @devopsborat

just in case you followed the wrong devops borat, it's @DEVOPS_BORAT (the other one is a spam bot).

Borat is human, a spambot is devops.

Re: OVH Incident in Strasbourg

#134

Post by seszett »

nkkollaw wrote: post #126
seszett wrote: post #40

Earlier quoted context omitted.

It's a collection of datacenters in Strasbourg.

Ah, gotcha. So, that one datacenter caused all other datacenters to die..?

It's supposed to be two separate incidents: power going down in Strasbourg, and fiber network equipment going down in Roubaix (the main center of OVH's network) due to a "software bug".

It's explained here https://twitter.com/olesovhcom/status/928587258583748609 in French, they might post an English-language translation soon.

Re: OVH Incident in Strasbourg

#135

Post by y4mi »

Gigablah wrote: post #86
contingencies wrote: post #79

To make error is human. To propagate error to all server in automatic way is #devops. - @devopsborat

Pfft network engineers have been at it way longer :p

Network failures are generally easier to recover from though. You just need to reconfigure the key nodes and everything is back in business.

If your CD pipeline deploys corrupt apps, even your production database can get compromised,forcing a full restore. No matter how long that might take

Thankfully,I didn't have to witness that yet.

Re: OVH Incident in Strasbourg

#136

Post by _wmd »

gyaru wrote: post #105
wiz21c wrote: post #104

Damn, every emergency power supply I have encountered (the big ones with fuel and hundreds of batteries) always fail to start when they have to... Why is that ?

People not actually testing emergency equipment.

While at $bigco we halted testing of generation equipment because it was sending DCs offline more often than it kept them up. Lawyers were involved, things got ugly

Re: OVH Incident in Strasbourg

#137

Post by viraptor »

holmb wrote: post #110
tmikaeld wrote: post #108

Earlier quoted context omitted.

Sorry, i didn't see the time stamps! You where first! :D

It would seem an ID of 15660524 would be submitted before 15660556, no?

Likely. But there's also a number of reasons why this may not be the case.

Re: OVH Incident in Strasbourg

#140

Post by fapjacks »

metafunctor wrote: post #29

Someone with access might wish to update the title of this post, because all OVH datacenters are definitely not down.

Yes, very important. I have two dedicated machines in different racks in Canada that were serving requests all night. I was also logged into both machines via SSH all night with no interruption.
Post reply on HN