Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
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".
Problems in the last 24 hours
The graph below depicts the number of Amazon Web Services reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Amazon Web Services users through our website.
- Website Down (59%)
- Errors (24%)
- Sign in (18%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Ciudad Jardín
|
Website Down | 2 days ago |
 Kyiv
|
Sign in | 1 month ago |
 Chennai
|
Website Down | 1 month ago |
 Point Pleasant Beach
|
Website Down | 2 months ago |
|
Little Rock
|
Errors | 2 months ago |
|
Atlanta
|
Website Down | 2 months ago |
Full Outage Map
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:
-
Pranjal Agrawal (@agrawalpranjal7) reported@AWSSupport I am still waiting for an update from AWS, as it has been 13 days since I raised the issue, and it remains unassigned.
-
Catdingo (@CattManii) reported@awscloud Is that after or way after losing millions of dollars due to uptime issues?
-
TheBlueDaisy (@diabendia) reported@mattsgarman @awscloud @amazon I’m having trouble getting my refund from Amazon, Matt! Please drop a name and phone number of someone who has the stroke to get this done!!
-
chaturfier (@chaturfier) reported@AWSSupport I was even just billed for this service that is now not working! Disgraceful!!! Distasteful! Sick! Fuckups!
-
Clint Jorgenson (@ClintJorgenson1) reported@AmazonHelp @amazon @awscloud The Customer Experience (CEx) company with absolute dismal CEx. Incorrect delivery notifications to customers is pathetic. Investigate this store and fix it.
-
Drew Tewell (@drewtewell) reported@DoorDash Is there an @awscloud outage? #DoorDash isn’t working.
-
Miguel A. Vega Segovia (@mavegasegovia) reported@AWSSupport @AWS URGENT: my AWS account 268140507056 has been WRONGFULLY SUSPENDED for ~48h — AFTER paying my invoice IN FULL (balance $0.00). My 100% digital business is completely DOWN, losing customers by the hour. 🧵
-
Kingdom of ElviSpeare (@ElviSpeareTV) reportedAll down: DoorDash. Spotify. GoDaddy. Verizon. Uber Eats. Amazon AWS. MLB Show. LinkedIn. Did someone cut the under water wires half way around the world? Possibly others.
-
vasik mansuri (@vasik_mansuri) reported@AWSCloud @AWSSupport We've been waiting for support for more than 3 hours today and spent hours yesterday as well. Our account was suspended after a password reset issue. Password has been reset multiple times, support case updated repeatedly, but still no response.
-
Tanner Scadden (@TannerSDev) reported@awscloud please help us asap your team suspended our account at the same time we got an email saying we have two weeks to address a problem with our root account. Cloudflare is down for us, and EC2 won't provision new instances. Our app is down. We serve hospitals. Please
-
Laurent Cligny (@lcligny) reported@awscloud Skill issue ?
-
esyx (@esyx0) reportedToday i got email from AWS that they can't approve my request for **** SES no explanation at all, only generic "During our evaluation, we identified some concerns that prevent us from approving your request. Due to security reasons, we are unable to provide specific details about our assessment criteria." has anyone had to deal with this? All i wanna use the SES for is transactional mails like verification, reset, notifications about your account etc @awscloud @AWSSupport Can you please help? At least tell me what's wrong so i can fix it, i genuinely have no idea
-
leapfrog (@leapfrogcl) reportedAWS Amazon is down. 😱🤯 @AWSSupport
-
Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reportedIs something wrong with Opus again today? Yeah. Def not running my bug fixer until this is fixed. It’s struggling. I just did AWS + CLI update but I think it was struggling before that. Practically unusable right now. I write one file to list and run one of my projects with bash trace. It messed up the project menu. There’s that M word again. But it fixed it. Very, very slowly. Next I added a menu option to trace the log in a separate step that I can watch in a different window. It’s building the exact same project list with the same script. It messed up the project list AGAIN. I mean it literally just wrote the exact same thing in another file. So I tell it to make it work like the other file. It is crawling. One line every 10 seconds feels like. I told it just do what you did in the other file you just created. It’s been many rounds. It is inserting variables referencing things it doesn’t need like the memory files and config files from the other projects when I never told it to do that and it has not reason to do that. It only needs to write one line to trail the debug log. What the heck? Time to walk the dog and hope it is fixed when I get back. Using AWS Kiro CLI + Opus 4.8 An older version of Kiro CLI but nothing has changed there so no reason for it to not work as good as it did yesterday. Will be updating shortly but the problem is something else. Oh there it is. Opus 4.8 not available. @AnthropicAI @awscloud @kirodotdev
-
AI Inc (@AiTesty5) reported@awscloud Normal people call this „skill issue“… come one AWS, you’re selling us this crap and then talk bad about it?
-
🇿🇦CN - Cracking News🇵🇹 (@walter_mashala) reported@awscloud @luis_usaa It’s good but will only server those who could afford using them, the world has more poor people than rich the people therefore it will work for the few.🤔
-
Amit Khera (@ai_amitkhera) reported@MatthewBerman They need not to fix other system vulnerabilities. They have to fix their system from its own. Now its clear that Amazon @awscloud is not secure as pretend to be. Now a clear risk is there when you are hositng your data in the system.
-
Chocobo (@chocobo2837) reported@awscloud Amazon complaining to the US government about the lastest frontier model and getting it shut down.
-
yapay zeko (@yesilliksepeti) reported@awscloud that is not an excuse of being behind ai race, it points a real problem of ai and its hype!
-
AbendStarr (@AbendStarr) reported@IAGovernor @awscloud @Cognizant Just out of curiosity will the citizens of Iowa have their taxes go down bc of these "savings"?
-
Tiffa (@TiffaJessi) reportedYo @awscloud u guys should totally idk maybe fix servers with @PlayApex because they’re TERRIBLE!!!!!!
-
Tejas Korde (@imTkorde) reported@AWSSupport @AWSstartups @AWSSupport It’s been over 13 days and I still don’t have access to my AWS account. The issue remains unresolved and now I’m about to lose my account and credits too. Really disappointed with how this was handled.
-
Astra (@0xAstra) reported@awscloud AWS is honestly a massive disappointment. You sign up, then discover basic customer support is locked behind a paid plan. Isn’t support supposed to be the most basic part of a cloud service? I didn’t pay for premium support, so a simple SES email permission request has been ignored for three days. I genuinely don’t understand how this is the world’s No.1 cloud provider. This experience is terrible.
-
Rudrakshya | Building Feedvoty (@RudrakshyaAi) reported@AWSSupport Our AWS account was suspended due to a billing issue. We've now paid all outstanding charges, but our production SaaS is still offline. We have an active support case (#178295929600096). We'd appreciate any assistance in expediting the review. Thank you.
-
Garratt Campton 🍄 (@gcampton) reported@AndrewChamb @awscloud It actually wasn’t able to do that, it could create new repos and PRs but not analyse and fix your own code. It would get downgraded. Sounds like you never used it.
-
Conor O'Neill (@conoro) reported@AWSSupport @AWSAI Attempting to use the new Gemma 4 in eu-central-1 via Curl. New error I've never seen before. "error":{"code":"access_denied","message":"Berm is not enabled for this account" What's Berm? model: google.gemma-4-26b-a4b
-
Ani (@nomad_on_run) reported@awscloud my ticket is open for more than 24hrs and nobody is yet assigned. I understand there is no SLA for basic support, but need assistance as i’m getting quota error even for a basic machine setup with 2 vCPUs
-
Ann O'Leary 🙄🤬 (@Panda6) reported@goodreads Hi - honest question - why is your site so very slow to load?? Can’t you get some @awscloud juice behind it??
-
Hershal Rao (@Hershal0_0) reported@awscloud anything to avoid hugging a server rack in a cold data center ever again
-
Mashood tried Ops (@fromcodetocloud) reported🤯AWS S3 Outage (2017) : In 2017, a routine maintenance task inside AWS turned into one of the most famous outages in cloud computing history. An engineer working on Amazon S3 executed a command with an incorrect parameter, causing more servers to be removed from service than intended. What followed was a chain reaction that affected thousands of websites and applications across the internet. The outage lasted around 4 hours, but the impact was far bigger than the downtime itself. Companies suddenly realized that services they considered independent were actually relying on the same underlying cloud infrastructure. Slack, Trello, Quora, and countless others experienced disruptions because a critical dependency had failed. The most interesting part? The incident wasn’t caused by hackers, hardware failures, or a sophisticated cyberattack. It was caused by a routine operational task performed by a human.