Live data from Hacker News

Our service is down because Msft Azure is down. This is how we chose to react.

modern-products.tumblr.com

31–40 of 67 posts

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#31
I didn't know what Soluto was, so I went on your main page to find out what it was while your service was down. All I saw was "Service Disruption :( We are experiencing problems with our cloud infrastructure More information..." Nothing else to click on but that one link for support. So when I clicked on it, still didn't know what it was and so I scrolled all the way down and clicked "About" then yet again I was greeted by the same alert. I understand your service is down, but does it have to take your whole site with information on your product with it just to show your service is down?

Anyways my 2 cents.

Regards.

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#32

I can recommend trying AppHarbor - we're striving to deliver a better .NET and Windows cloud platform. Feel free to shoot me an email (rs@appharbor.com) if there's anything I can help with.

Its just too expensive, you cant host your custom domain name on free instance. And there's nothing between 0 and 50$. I'm waiting for prices of azure web sites, hopefully it would compare to shared hosting prices.

You can add custom hostnames to the free instance for $10/month

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#33

I didn't know what Soluto was, so I went on your main page to find out what it was while your service was down. All I saw was "Service Disruption :( We are experiencing problems with our cloud infrastructure More information..." Nothing else to click on but that one link for support. So when I clicked on it, still didn't know what it was and so I scrolled all the way down and clicked "About" then yet again I was gree…

That's right. It's double-bad when things like that happen during the weekend so time-to-reaction is slower. All will be better tomorrow.

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#34
post #21
post #18

When can we move beyond blaming a cloud service and just owning up to the decision? Soluto chose to use Azure and knew they were taking a risk. It's their fault for choosing to use Azure, and unless they signed for a 100.000000000% uptime guarantee (which I'm sure they didn't, given no one would give such a guarantee) they have to own up to any faults. This extends to those services that blames AWS as well. It's not…

Azure offers a SLA with a 99,95% uptime guarantee for computing instances and a 99,9% uptime SLA for storage. If they do not meet this SLA you will get your money back. You can read more about it at www.windowsazure.com/en-us/support/legal/sla/

SLAs are worthless, because just getting your money back does nothing to repair the damage to your business. It's like if someone in your family died from food poisioning and the restaurant gave you back your $10 for lunch.

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#35
post #21
post #18

When can we move beyond blaming a cloud service and just owning up to the decision? Soluto chose to use Azure and knew they were taking a risk. It's their fault for choosing to use Azure, and unless they signed for a 100.000000000% uptime guarantee (which I'm sure they didn't, given no one would give such a guarantee) they have to own up to any faults. This extends to those services that blames AWS as well. It's not…

Azure offers a SLA with a 99,95% uptime guarantee for computing instances and a 99,9% uptime SLA for storage. If they do not meet this SLA you will get your money back. You can read more about it at www.windowsazure.com/en-us/support/legal/sla/

[deleted]

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#37

Perhaps this is part of your current problem with Azure, but is it possible to retain some part of your frontpage during an outage like this? Or failover to a static page with a basic description of the service? Your support site seems to look ok. I only make the suggestion because I was not aware of Soluto. I went to your homepage and see the outage notice and a link to support. I still have no idea what your servic…

Good point :)

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#38

This made me think of the Netflix outage the other day. When people like my non-technical parents say things like, "did you hear Netflix went down," they don't care that it was Amazon that really went down. I don't use Soluto, so I don't know their customers, but I doubt they care that Microsoft has dropped the ball. It's a chance we take when we deploy to the cloud, and services like Heroku only compound it because…

A classic case of: "you can't outsource responsibility".

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#39
post #13

This is a nice gesture, but I prefer the services I use to take responsibility for their provider and technology choices. Your customers don't care that Azure is down, they only care that they can't do whatever they were trying to accomplish. This isn't Azure's fault. It's yours. Don't pass the buck.

And if all they said was they were experiencing difficulties you'd see people complaining that they aren't giving any indication as to what the problem is.

The site is down because their provider is down. This is, as someone else stated, a fact. They told you that and that is really all they can do. They have to wait just the same as you do, for the same thing.

> This isn't Azure's fault.

Yes it is. The alternative is to pay more (a lot more) for projects to host all their own servers and storage and backups. That would be the end of a great many small to medium companies.

Re: Our service is down because Msft Azure is down. This is how we chose to react.

#40
post #14

Maybe a noobish question, but in the future, is there anything other than need for preparation, that prevents you from having a backup spun up on say AWS or another service provider? It seems like a prudent step to take.

It's the entire service, not a bunch of files. When Netflix went down due to AWS outage, could you image them just "restoring a backup" on rackspace and running just like that?

I've got several services (both consumer and commerical) running on Azure and right now I just see some issues with storage in the south. Web/Worker, VMs, Sql, etc. are running just fine it appears. Any pointers on where I should be looking for potential issues?
Post reply on HN