Live data from Hacker News

IBM Cloud was down, as well as their status page

cloud.ibm.com

111–120 of 201 posts

Re: IBM Cloud was down, as well as their status page

#112
post #36

Seems pretty dumb to host a status page in a way that it could go down, when it should be a static page that is trivially hosted on CDN's worldwide.

You can’t cache it for that long though. A better approach is to have it hosted on a different cloud platform. If you really care, you’ll set it up on a different domain and nameserver as well with a long lived redirect (cached on CDNs) from the usual status.example.com or example.com/status.

Thanks; you're right - the caching would be a problem, so your solution makes more sense.

Re: IBM Cloud was down, as well as their status page

#114
post #87

So what are HNers using IBM Cloud for and where do you see that it has an edge over AWS offerings (where an overlap exists, obviously)? (I figure either you’re in devops and you are putting out fires too busy to read this thread or you’re not and your work is halted because of the incident so you might have time to read and reply ;)

We used Softlayer (rebranded to IBM Cloud, and affected by this) at my last job. For the most part, their service pretty much just works; clearly not today. :) We had a couple thousand bare metal servers, and barely used any of their API stuff. As with any facility, there were occasional issues with electrical transfer switches, core router failures, fiber cuts, etc. Stuff happens, but we got pretty good communicatio…

You guys were one of the best use cases for the SL model, which really hasn't changed in 10+ years. You had very few dependencies on the less-reliable (read: all of them) services inside the SL stack and mostly managed everything on box and in software. In a few POPs you guys were running about 50% of the total SL backbone bandwidth. There were a lot of sad panda hats when you guys started to transition away.

Re: IBM Cloud was down, as well as their status page

#119
post #80

Earlier quoted context omitted.

[deleted]

Does it smell of fuckup, or of intentional BGP hijack?

If it was a BGP peer who normally sends you 3 prefixes with under a /20 in aggregate and they suddenly started sending you a whole table, or if you allowed a peer to send you a default route, then both of those are highly avoidable through session configuration and filtering.

If the route which caused the madness came in via a large settlement-free peer (like a big eyeball/access network) or a transit (which is probably giving you the whole table) that's entirely another story.

Post reply on HN