141–150 of 178 posts
Earlier quoted context omitted.
Wow, comparing that to AWS is staggering! https://cloudharmony.com/status-for-aws
It's not as if AWS has never gone down ( http://aws.amazon.com/message/65648/ ). It just hasn't had a major outage in the last 30 days.
Azure support is probably the worst one I had ever deal with. When my account (and service itself) stopped working, I haven't received any email. When I tried to sign in, all I got was some generic error saying "There's something wrong with your account". My services of course were down and I couldn't do ANYTHING. I've contacted the support to learn that my account has been blocked (!) because there was some suspicio…
I had a similar situation with DigitalOcean. Droplets were taken offline with no notification whatsoever, only answered after I submitted a ticket. This has happened to me twice.
The idea of cloud storage being down is less of an issue - I don't like it, but I understand it. What bothers me about this is: 1. I was never notified of the outage. I noticed it myself when attempting to log into one of my VMs and then started looking for status updates. Sadly, the best status updates I got were here on Hacker News. 2. When my servers did come back up, at least one of my IP addresses had changed, w…
I think that's been largely dispelled.
I can't find the link right now unfortunately but I remember a post looking into DNS propagation realities from either this or last year, and they found that overwhelming majority of DNS servers they tried (99%+) respected the TTLs set exactly as they should. *
My personal rule of thumb is, if it hasn't propagated within an hour, I need to look at it again because I messed up.
Tools like this [1]are invaluable when you're paranoid about whether your new record has propagated.
[1] https://www.whatsmydns.net
* ugh. Does anyone know which post I'm talking about? My google-fu is failing me hard.
The idea of cloud storage being down is less of an issue - I don't like it, but I understand it. What bothers me about this is: 1. I was never notified of the outage. I noticed it myself when attempting to log into one of my VMs and then started looking for status updates. Sadly, the best status updates I got were here on Hacker News. 2. When my servers did come back up, at least one of my IP addresses had changed, w…
Sadly this is a common situation. They appear to hold off making any public notice (including often on their own "service dashboards") until support forums are screaming with upset users. Google App Engine has had numerous outages like this, the only one I can find any public documentation for being a 6 hour outage in 2012: http://googleappengine.blogspot.co.uk/2012/10/about-todays-a... (and let's not forget the old-…
The App Engine team has a proactive policy about posting about downtime:
https://groups.google.com/forum/#!forum/google-appengine-dow...
Since the team highlights basically anything that looks like it is impacting customers, the issues don't always warrant a stand-alone blog post, but you'll notice that generally speaking the last post in each thread is a full public post-mortem with diagnosis and remediation.
Let me know if there's more you think might be useful for you as a GAE customer. Thanks!
Azure support is probably the worst one I had ever deal with. When my account (and service itself) stopped working, I haven't received any email. When I tried to sign in, all I got was some generic error saying "There's something wrong with your account". My services of course were down and I couldn't do ANYTHING. I've contacted the support to learn that my account has been blocked (!) because there was some suspicio…
Judging by how cloud services "frequently" go down when everything is normal, it makes me wonder what would happen in case of a real problem (volcano eruption, social unrest, nuclear disaster, alien invasion ...). I still don't get the cloud infatuation, and no you don't have to get off my lawn, I'm "only" 36 (yeah I know, in IT I'm already a dinosaur).
Put your servers in different regions, use Azure/Google, BlueMix/AWS, or even hybrid cloud, do something. Have a DR plan.
Earlier quoted context omitted.
2. Azure does not guarantee that you keep your ip address by default. You should configure a cname if you use Azure Websites or get a reserved ip address, available with Cloud Services
Also as I found out, set the TTL on your CNAME very low. Also this is a PITA if you use the @ entry in your DNS.
Mistakes happen, services go down, I can get over that. What matters is how its dealt with. At the moment I would not want to be an Azure customer dealing with 9 hours+ downtime whilst MS are saying everything is great. At the very least change it to "Having some issues" or similar!
The idea of cloud storage being down is less of an issue - I don't like it, but I understand it. What bothers me about this is: 1. I was never notified of the outage. I noticed it myself when attempting to log into one of my VMs and then started looking for status updates. Sadly, the best status updates I got were here on Hacker News. 2. When my servers did come back up, at least one of my IP addresses had changed, w…
> which, as everyone here no doubt knows, can take up to 48 hours to propagate I think that's been largely dispelled. I can't find the link right now unfortunately but I remember a post looking into DNS propagation realities from either this or last year, and they found that overwhelming majority of DNS servers they tried (99%+) respected the TTLs set exactly as they should. * My personal rule of thumb is, if it hasn…