61–67 of 67 posts
Earlier quoted context omitted.
How is this different from, say, a coffee shop saying "sorry, we're closed because the electricity went out"?
I guess the difference would be that there is usually only one electric company that can supply you with power.
Earlier quoted context omitted.
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/
They've already blown that SLA - for the year. Now how much of my money do I get back?
What is the extent of this outage? There isn't much info on Twitter or elsewhere. The Azure service status dashboard shows an issue impacting "Storage [South Central US]". Is that service like S3 or EBS or something entirely different?
What is the extent of this outage? There isn't much info on Twitter or elsewhere. The Azure service status dashboard shows an issue impacting "Storage [South Central US]". Is that service like S3 or EBS or something entirely different?
Earlier quoted context omitted.
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.
Are you trying to tell us that proper automated failover systems take the weekends off?
Earlier quoted context omitted.
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 i…
It's a myth that dedicated hosting in several geographically distant data centers really costs that much more than cloud computing. With a little bit of care, it's quite easy to get very good value from such hosting, with far more control over it. Outages like this could be easily avoided, or at the very least dealt with much quicker. It would not be the "end of a great many small to medium companies" were they to us…
"Why didn’t we just fail over? We do have geo-replication for Windows Azure Blobs and Tables, where the data from US South is geo-replicated to keep another replica set of the data in US North. We have chosen at this time not to failover, since we believe we can bring back the primary storage stamp in US South in place. One of the advantages of recovering in place is it avoids losing the Windows Azure Queue data in that stamp, since Windows Azure Queues is not being geo-replicated at this time (we are working towards turning that on)."
Earlier quoted context omitted.
You can add custom hostnames to the free instance for $10/month
Can you explain to us why such basic functionality is so expensive? Is there a legitimate technical reason for the cost, for example? Or is it subsidizing some other service? Or is it that high just because some people are foolish enough to pay that much for it?