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 (67%)
- Sign in (17%)
- Errors (17%)
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 | 17 days ago |
 Kyiv
|
Sign in | 2 months ago |
 Chennai
|
Website Down | 2 months 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:
-
Alex Hooper (@AlexHooper78640) reported@AWSSupport our entire system is returning 500s - what’s the eta on a fix for this?
-
That Other Hecate (@HecateKeys) reported@OwenGregorian 1) Forgets how DNS works. AWS goes down for days. 2) Forgets how arithmetic & metering works. Trillion-dollar bills for scant usage. @awscloud Regretting all those mass layoffs of your veteran engineers yet?
-
Nil (@slowalgorithm) reported@awscloud How are you planning to compensate all your customers who panicked and started deleting resources since the email was legit and there was not a second email notifying of the issue. Your support bot itself claimed the expenses were legit.
-
Revy (@RevyDown) reported@liberdus @Pirat_Nation Think Amazon AWS went down last year as well. You would think that would have been a wakeup call but noo.
-
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
-
Ryan Varghese Mathew (@RyanVarghese14) reportedHi @awscloud @AWS I am currently facing issues from regarding certain payments. And despite incessantly reaching out on the support team and the email, I have been charged and there has been no formal support extended. I know you guys can do better than this.
-
devastatindave.eth (@NftCelestials) reported@awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually
-
Jeff B. Vockrodt (@JeffBVockrodt) reported@AWSSupport You should send follow up emails alerting all your customers to this issue. I woke up to a $719 million billing estimate which although absurd conjures a potential nightmare of getting it worked out
-
Silksteele (@silksteele) reported@adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.
-
Julley Thai (@julleybuilds) reported@kunalstwt @awscloud @FrancescoCiull4 rust is a steep climb but the compiler error messages honestly make it worth it once u get the hang of it
-
Marek Serafin (@stoprocent) reported@DerDerDaIst @AWSSupport After they fix it, I'm setting up deny all policy.
-
S_A.A | WordPress Developer | Ai (@saafolabi_me) reportedThe 3-2-1 backup rule, applied to web hosting: 3 COPIES of your data 2 DIFFERENT storage types 1 OFFSITE location What this looks like in practice: Copy 1: Daily cPanel/WHM backup → stored on server Copy 2: Weekly backup → synced to Amazon S3 or Backblaze B2 Copy 3: Monthly snapshot → downloaded locally to your own machine Storage type 1: Server disk Storage type 2: Object storage (S3/B2) Offsite: S3 and your local machine are not on the same server The part almost nobody does: → RESTORING a backup to verify it works An untested backup is not a backup. It's an assumption. Once a month: → Pick a client site → Restore yesterday's backup to a staging environment → Confirm the site loads and the database is intact → Document the restore time If you've never done this, the first time you need it is not the time to find out it doesn't work. When did you last successfully restore from a backup?
-
AntDracula (@ant_dracula) reported@_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error
-
Indrani Som (@indrani_som2004) reported@Anjishnu46 @AWSSupport @AWSSupport look into this issue
-
Ayush Sanj (@AyushSanj) reported@taashuu_ @TeamShiksha @awscloud Looks like internal aws issue, big issue tho. Millions 🥲
-
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.
-
Har (@duckboy1909) reported@awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon
-
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?
-
Ing. Mario Varón M.Sc (@ma_varon_col) reported@AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...
-
SwarmOne.ai (@swarmoneai) reportedOpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud
-
dale (@daleverett) reported@pkyanam @AWSSupport bro so its an error>???
-
Nexzul (@NexzulX) reported@awscloud @PreciselyData Bedrock only has Anthropic models and a bunch of obsolete open source models. You need to fix this.
-
Donna Paulsen (@donnapaulparody) reported@VeryCoolGuy6 @awscloud Check the issues that happened in last 6 months and diagnosis/cause of the issue.
-
Eszter Morvay (@eszter_morvay) reported@AWSSupport Also - apologies for the DM issues, i just changed my settings, so DMs should work now
-
Kishan (@Kishan200615) reported@AWSSupport Please help resolve this issue as soon as possible, as I urgently need my AWS Associate certification. If you need any additional information, please contact me. Thank you.
-
GamerUP (@GamerUPGaming) reported@TheRavenHelm man... are you detective seeds right? this is a new profile name ? whatever.. the "digital only direction" was announced more than 3 weeks ago.. not last week.. PSN servers are hosted by Amazon AWS, and amazon AWS had some disruptions today, they already solved the issue.
-
Ajith (@iamarulajith) reported@F1 @awscloud Actually surprised to see the good start by Max. I thought he would bog down again but not this time.
-
D (@D8118199174282) reported@awscloud No, you still haven’t compensated users for the cost bug error
-
deibeat (@deibeat_13) reported@AWSSupport I did the same exactly, and really panicked when I saw that, thought someone got access or something. Tried to contact billing support, removed s3 bucket, turned off a personal website using it, asked Claude for guidance until I finally found it was a global issue…
-
Edward Donner (@edwarddonner) reported@okko @awscloud @AWSSupport That's why it's opt in. Netflix would likely not opt in and be fine with the risk. You could join them if you wish. I would prefer to face an outage if AWS has another billing disaster than have unbounded exposure.