4 ms·
If this outage is solely caused by an expired SSL certificate then this is really bad. It makes Azure look like amateur hour (even though it's definitely not).
by gabbo 14y ago
If this outage is solely caused by an expired SSL certificate then this is really bad. It makes Azure look like amateur hour (even though it's definitely not). This may be acceptable for a smaller operation, but not Microsoft's cloud platform. There should be processes (manual and automated) to deal with this.
On the bright side, after this you know they're not going to make the same mistake twice.
- niggler 14y ago"It makes Azure look like amateur hour (even though it's definitely not)" Why do you think Azure is not?
- gdc 14y agoDo you think that it is?
- niggler 14y agoYou can't deny that the current issue is certainly not something you would expect of a serious offering
- gdc 14y agoEvery major cloud offering on the market has had outages that were traced down to silly issues. I'm not sure if your dislike is targeted at just Azure, or the cloud in general.
- niggler 14y agoI'm always apprehensive of outsourcing critical business infrastructure without a failover plan, and I find the excuse "amazon is down" or "azure is down" unsatisfying (especially when its a service customers pay for)
- suresk 14y agoHaving a "hot spare" cloud provider is going to be so complex and expensive that it probably would kill the idea of using Azure, Amazon, etc for most companies. Unless you run your own DC, you are still outsourcing part of your infrastructure to a colo facility, which will not be immune to power and connectivity issues, and of course, issues with your setup. Saying "<cloud provider> is down" certainly isn't very comforting, but if the aggregate downtime is less than if you were running your own setup, I'm not sure that being powerless in the event of downtime is reason enough to not use them.