The main issue appears to be DynamoDB Here's a copy from the status page. 3:00 AM PDT We are investigating increased error rates for API requests in the US-EAST-1 Region. 3:26 AM PDT We are continuing to see increased error rates for all API calls in DynamoDB in US-East-1. We are actively working on resolving the issue. 4:05 AM PDT We have identified the source of the issue. We are working on the recovery. 4:41 AM PD…
6:19 AM PDT The metadata service is now stable and we are actively working on removing throttles. 7:12 AM PDT We continue to work on removing throttles and restoring API availability but are proceeding cautiously. 7:22 AM PDT We are continuing to remove throttles and enable traffic progressively. 7:40 AM PDT We continue to remove throttles and are starting to see recovery. 7:50 AM PDT We continue to see recovery of r…
AWS US East is experiencing high error rates on several services
121–130 of 184 posts
Re: AWS US East is experiencing high error rates on several services
#122This seems like another reason to not rely on Amazon-specific services, other than the obvious vendor lock-in. At least in the event of an instance outage you could conceivably migrate off Amazon to another VPS provider. No one using DynamoDB has an alternative.
Re: AWS US East is experiencing high error rates on several services
#123For ADHD I would recommend Concerta/Ritalin/Adderall; that would enable you to read for not just a few seconds more but even minutes more before you judge. (I'm not joking here, I'm using 36mg Concerta for about about 4yrs now. Before that I also often came across as an asshole.) There is also a less evasive way of improving your online communication quality: http://www.paulgraham.com/disagree.html
Re: AWS US East is experiencing high error rates on several services
#124Earlier quoted context omitted.
From Heroku Status Page: > Our service provider is still working towards resolution of this issue. We will update when we have news, or in 1 hour. I wonder why they don't tell that AWS is their service provider. Is it wrong to make the information less obscure?
Because it is kind of awkward PR for Salesforce: come build on our platform! Oh by the way we haven't even moved Heroku, a company that we bought 4 years ago, over to it yet.
Re: AWS US East is experiencing high error rates on several services
#125Re: AWS US East is experiencing high error rates on several services
#126Earlier quoted context omitted.
Because it is kind of awkward PR for Salesforce: come build on our platform! Oh by the way we haven't even moved Heroku, a company that we bought 4 years ago, over to it yet.
Why move it if it works fine as-is? I think Waze was bought by Google in 2013 and AFAIK, they're also still in AWS.
Re: AWS US East is experiencing high error rates on several services
#127This is manifesting itself as downtime for a lot of companies, including Heroku: https://status.heroku.com If you want alerts on this sort of thing, my side project StatusGator https://statusgator.io will alert you when services post downtime on their status pages. My dashboard blew up this morning with a ton of red and yellow as soon as Amazon started flaking. Edit: I suppose it's time to invest in a multi-region se…
From Heroku Status Page: > Our service provider is still working towards resolution of this issue. We will update when we have news, or in 1 hour. I wonder why they don't tell that AWS is their service provider. Is it wrong to make the information less obscure?
It's because Heroku's choice of vendors shouldn't matter to their customers. They see it as an implementation detail, and their responsibility to manage.
So I don't think that's an obfuscation. The people I know at Heroku all have an attitude of, "The buck stops here."
Re: AWS US East is experiencing high error rates on several services
#128This seems like another reason to not rely on Amazon-specific services, other than the obvious vendor lock-in. At least in the event of an instance outage you could conceivably migrate off Amazon to another VPS provider. No one using DynamoDB has an alternative.
How would this have helped? In the event of an AWS outage, you have all-hands of one of the biggest tech companies in the world working to fix your infrastructure. This outage lasted a few hours, wouldn't it take you that long to switch providers anyway? If you don't abdicate responsibility for maintaining the infrastructure, you lose a lot of the operational benefits of using a cloud service...in general, I think it…
No, they are fixing their infrastructure. The point here is that all single provider systems are destined for periodic failure. Not relying on one single provider is, in theory, a service's means of providing higher reliability. This is the general argument for regions and availability zones on Amazon, but that relies on trusting there is no single point of failure with the system (i.e. inside Amazon).
I've worked for several companies who run the majority of their services on AWS, yet maintain functional systems on other providers in the case of an AWS outage.
Re: AWS US East is experiencing high error rates on several services
#129What is happening to stock price? oh; its sunday; forgot we can't trade.
Re: AWS US East is experiencing high error rates on several services
#130Earlier quoted context omitted.
failure tolerance is an alien technology for amazon...
that's completely untrue. there are many ways to do fault-tolerance in AWS. it's expensive, but it's possible. netflix even goes as far as simulating the failure of entire aws regions in their simian army testing suite: http://techblog.netflix.com/2011/07/netflix-simian-army.html That's why Netflix stays up when us-east or us-west are down.