Amazon Web Services Outage Map
The map below depicts the most recent cities worldwide where Amazon Web Services users have reported problems and outages. If you are having an issue with Amazon Web Services, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Amazon Web Services users affected:
Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Ciudad Jardín, MEX | 1 |
| Kyiv, Kyiv City | 1 |
| Chennai, TN | 1 |
| Point Pleasant Beach, NJ | 1 |
Check Current Status
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Amazon Web Services Issues Reports
Latest outage, problems and issue reports in social media:
-
Erin (@erinEncoded) reported@awscloud This is tone deaf. It wasn’t funny. It was upsetting. It reduced my trust in your systems, testing, and ability to roll back critical errors. I didn’t laugh. Why are you?
-
Matthew Feinberg (@thewebbie) reported@infoscav @awscloud 28 Billion! AWS has acknowledged there is a problem with the billing console.
-
J Bret Edwards (@jbecompslns) reporteddid @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.
-
PositiveVibes (@KPTheFighter) reported@awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws
-
Maurizio Santamicone (@santamm) reported@awscloud And while you fix it, you can credit us for those amounts.
-
Nik Tiwari (@nikhil20077) reported@awscloud Its been 22 days. My issues related acces to amazon bedrock is not resolved. I am frustrated with no help and arbitrary support. AI text generated is not help. Shameful @AmazonHelp #CustomerSupport #CustomerComplaint I replied in Dm nothing happened.
-
AntDracula (@ant_dracula) reported@ngriffin_uk @perezcarreno @awscloud You never built anything of consequence, ever. This could have set off circuit breakers where people would automatically shut down and nuke services when a bill gets out of control because AWS themselves doesn’t have a spend cap. Lower your tone.
-
Damon (@agaphto) reported@sorower01 @awscloud Also just got a $3m bill. There's an AWS issue going on
-
Silksteele (@silksteele) reported@adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.
-
riffy (@riffydays) reportedToday, a rare break outside ended when a $90B bill hit my inbox and sent me rushing back I learned it was a bug from AWS Support on X—but finding out this way is a problem. If the bill came by email, why not the notice? Premium pricing. Anything-but-premium service @AWSSupport
-
Soru Soran Adam (@SoruSoran_Adam) reportedI felt really bad when I switched from Azure DevOps to AWS. Why did AWS create such terrible interfaces for DevOps / Dev Teams ? Constantly defining permissions with JSON is so tedious. It'll take a little while to get used to it. @awscloud @Azure
-
nikhil tyagi (@tyaginikhil50) reported@awscloud Is cloudfront down?
-
Eimantas (@TidusLT) reported@AWSSupport Thanks for nothing, i think you should have a global public post, on how much account needs to spend, before being able to use new models, because support answers on free plans is taking too long for such a simple error, which does not explain anything
-
Dawid Pura (@puradawid) reported@AWSSupport @awscloud Please, before you will do anything else, can you just deploy a warning on cost explorer that those figures are inaccurate and there is an undergoing investigation? People seeing this can get into very big trouble because of fear, other emotions...
-
Arash Sadrieh (@ArashSadrieh) reported@AWSSupport Hi @mattsgarman our whole service is down for almost 3 hours, would appreciate some help here ,eta on fix would be great
Check Current Status