3 ms·
My side project StatusGator monitors status pages (including IBM's ill-fated page) and I'm seeing more than 10% of the nearly 800 services we monitor having an
by colinbartlett 6y ago
My side project StatusGator monitors status pages (including IBM's ill-fated page) and I'm seeing more than 10% of the nearly 800 services we monitor having an outage right now.
So it appears to affect anyone who depends on IBM Cloud.
- Jedd 6y agoBig fans of StatusGator here. Do you have similar %'s of monitored cloud services that have gone off the air during other providers' outages?
- colinbartlett 6y agoThanks and that's a GREAT idea for some detailed analysis. I have been trying to make better use of the 5+ years of status page history stashed in the cupboard.
- bigiain 6y agoThis is something I'd totally read. (You should headhunt the guy at BackBlaze who does their hard drive stats blog posts, and release this data analysis quarterly!)
- atYevP 6y agoYev from Backblaze here -> please do not do this, we really like him.
- brian_herman__ 6y agoYeah I think the backblaze does great work for backblaze for their hard drive report I can’t wait for him to talk about the WD SMR fiasco!
- bigiain 6y agoHow about: (You should contact the guy at BackBlaze who does their hard drive stats blog posts, and pay him to do this for you as a side hustle - and release this data analysis quarterly!) :-)
- darkteflon 6y agoOnly on HN.
- bberenberg 6y agoI really wonder how people get value out of a meta status page when my experience is that status pages are often incorrect about what the actual status is. Whether they're manually updated, or it's a case of "your 9s are not my 9s", it seems like a compounded broken telephone problem.
- pas 6y agoProbaly it's great to have some very big picture overview. Both in scope ("all" the cloud, and both in time as in "all" time, and maybe there's even some value in looking at the correlation of these). Maybe it helps with doing a sanity check before picking a provider. And, I guess, at a basic level it helps with accountability/transparency.
- o-__-o 6y agoWhen we started broadcasting status checks we thought it would be a great way to let users know what's happening behind the scenes. Then it turned out a lot of our happenings were self-inflicted so rather than being less transparent by way of less posts, we just tweaked our status outputs. "We are experiencing an event in <SOME VERY HIGH LEVEL SERVICE>" x1042. After we perform our RCA then we may post a blog about it or a short PR blurb The last time we went down I questioned out loud the point of the status page and the general consensus was for others to be able to reference our outage.