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

Microsoft Azure Outage

azure.microsoft.com

Post reply on HN
Print view View original

21–30 of 178 posts

Re: Microsoft Azure Outage

#21

Post by zaroth »

That status table with all the randomly located green checks is painful to look at... I guess a green check in the 'Global' column implies a green check in all location specific columns? But what about all the rows which have no Global green check, but most columns are still empty? Are those regions where the service is not deployed? Can we gray out those boxes or something if they are 'N/A'?

Also, funny if you try to zoom out in Chrome to see the whole thing, the row headers get out of alignment.

Why would I want to 'X' out specific rows/columns in the table? It was so complicated to begin with, someone thought adding more complication through end-user customization was a good idea? I just noticed, you can even expand some of the rows...

Seriously, a status page should tell you either "It's up" or "What's down". It's not even showing history over time, this is just a snapshot. The text at the top directly contradicts the icons in the table, making the whole thing even more ridiculous.

The footnote at the bottom is the best, "The Australia Regions are available only to customers with billing addresses in Australia and New Zealand." Thanks for that useful nugget! /s

Re: Microsoft Azure Outage

#22

Post by jedgrant »

Regretting the decision to go with Azure. Talk about terrible timing. We have media outlets interested in our site, we send info and the site is dead. Talk about a crap first impression.

Re: Microsoft Azure Outage

#23

Post by tawy1 »

zaroth wrote: post #21

That status table with all the randomly located green checks is painful to look at... I guess a green check in the 'Global' column implies a green check in all location specific columns? But what about all the rows which have no Global green check, but most columns are still empty? Are those regions where the service is not deployed? Can we gray out those boxes or something if they are 'N/A'? Also, funny if you try t…

History: http://azure.microsoft.com/en-us/status/#history

Re: Microsoft Azure Outage

#24

Post by unclesaamm »

zaroth wrote: post #21

That status table with all the randomly located green checks is painful to look at... I guess a green check in the 'Global' column implies a green check in all location specific columns? But what about all the rows which have no Global green check, but most columns are still empty? Are those regions where the service is not deployed? Can we gray out those boxes or something if they are 'N/A'? Also, funny if you try t…

Running Chrome 38.0.2125.111 m, zoomed out row headers look fine

Re: Microsoft Azure Outage

#25

Post by craigvn »

jedgrant wrote: post #22

Regretting the decision to go with Azure. Talk about terrible timing. We have media outlets interested in our site, we send info and the site is dead. Talk about a crap first impression.

It is totally frustrating, but at the end of the day similar outages happen with all cloud providers.

Re: Microsoft Azure Outage

#26

Post by photorized »

I feel like an idiot. MS featured my Azure startup today, quoting me about overall stability etc (which has been the case for us, until today). They then proceeded to go down, taking all our production systems with them.

(yes we do have AWS, too)

Sigh.

Re: Microsoft Azure Outage

#28

Post by photorized »

jedgrant wrote: post #22

Regretting the decision to go with Azure. Talk about terrible timing. We have media outlets interested in our site, we send info and the site is dead. Talk about a crap first impression.

I feel your pain. My startup was featured on TechNet today, I was quoted saying how great Azure worked for us so far... lots of folks were checking us out, and then Azure went down hard, taking our production systems with them. Talk about negative publicity.

Re: Microsoft Azure Outage

#29

Post by photorized »

teovall wrote: post #12

The postmortem for this should make for a good read. How does storage go down in eleven regions at once?

I suspect a human config error. I don't see how else multiple services, in multiple regions, can all be affected at once.

Looking forward to the post mortem.

Post reply on HN