2 ms·

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

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.

vim_wannabe 9y ago
Wouldn't this require that there be a very limited amount of things that can go wrong? Unless by stronger you mean some kind of a change in mentality over care for the service, but that would probably have a limited lifespan until it's back to normal.
- zaarn 9y ago
  Personally, I like to know how a service fails and recovers. If a service never fails then I don't know how well they can recover. I don't know anything about their failure mode. In this case, I'm learning how OVH handles failure modes, how well they handle it, etc. I can observe how they will treat such things in the future.
cm2187 9y ago
Not saying this is the case here but that's also sometimes where you spot amateurism and should run away. I remember a host provider a long time ago (15y) who was storing its backups on the same machine as the main data. Guess how I figured out!
- PuffinBlue 9y ago
  Oh man that sounds bad! You're right, sometimes these events do expose the inability to handle failure and you're right that that means walking away. Thankfully many times we're reminded that there are good people out there working hard against difficult constraints and they finally get their chance to do things 'correctly' in the wake of the SHTF.
r1ch 9y ago
OVH are very open about their outages and root causes. Even routine maintenance tasks are cataloged with updates at http://status.ovh.net 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.

vim_wannabe 9y ago

Wouldn't this require that there be a very limited amount of things that can go wrong? Unless by stronger you mean some kind of a change in mentality over care for the service, but that would probably have a limited lifespan until it's back to normal.

zaarn 9y ago
Personally, I like to know how a service fails and recovers. If a service never fails then I don't know how well they can recover. I don't know anything about their failure mode. In this case, I'm learning how OVH handles failure modes, how well they handle it, etc. I can observe how they will treat such things in the future.

cm2187 9y ago

Not saying this is the case here but that's also sometimes where you spot amateurism and should run away. I remember a host provider a long time ago (15y) who was storing its backups on the same machine as the main data. Guess how I figured out!

PuffinBlue 9y ago
Oh man that sounds bad! You're right, sometimes these events do expose the inability to handle failure and you're right that that means walking away. Thankfully many times we're reminded that there are good people out there working hard against difficult constraints and they finally get their chance to do things 'correctly' in the wake of the SHTF.

r1ch 9y ago

OVH are very open about their outages and root causes. Even routine maintenance tasks are cataloged with updates at http://status.ovh.net 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.