Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
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 (71%)
- Sign in (14%)
- Errors (14%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Sign in | 9 days ago |
|
|
Website Down | 14 days ago |
|
|
Website Down | 17 days ago |
|
|
Errors | 29 days ago |
|
|
Website Down | 1 month ago |
|
|
Website Down | 2 months ago |
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:
-
Aqib Ansari (@Aqib_Ansari_) reported@AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience
-
The AI Therapist (@TheAIShrink) reported@MikeLongTerm @amazon @awscloud EC2 on AMD CPUs. The cloud bill goes down, the margins go up. aws is quietly fixing its cost structure while everyone watches the models. smart
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.
-
mubs (@xmubsx) reported@AWSSupport MFA team is in-house team or outsourced. This is not acceptable. It has been 3 months. In June '26 this issue started. If the MFA device or app is out of sync. How is it my problem. This is aws issue. How can you guys ignore a genuine issue like this. All articles are useless.
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
Robat Das Orvi (@orvi_onethread) reportedDoes @awscloud have any real people in support? 😤 Frustrated after trying to reach a human for over an hour. Our server is completely down right now, and we can't get through. Terrible experience. We might finally have to switch away from AWS.
-
Abdulkadir | Cybersecurity (@cyber_razz) reportedClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.
-
Dan Lynch (@danlynch) reported@QuinnyPig @awscloud I need to sign in with LEGO 😎
-
Graham Christensen (@grhmc) reported@apparentorder @QuinnyPig @awscloud I'm sure they'll fix it after they're done at the discotheque
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport @AWSSupport Day 7.Production still down, Case still unresolved. Yesterday you said it was "forwarded internally for review" that's the third different phrasing for the same non-answer. I'm not asking for updates anymore. I'm asking: who owns this case, and when will it be fixed?
-
Lori-Colorado (@lori_colorado) reported@marklevinshow The future, I bet: Giant Data—owner/consumers* long-term goal (5-10 years) Replace all of the servers in the AI data—mega center barns. Then they won’t need all these monster consumers of land, water, electricity. They will be empty silent mausoleums of AI’s startup period. * Meta, Open AI/Oracle, xAI, Microsoft, Amazon AWS, and Google. Reminds me of Jonathan Winters in The Loved One (1965) looking down from his helicopter over his empire of corporate cemeteries… “ I’ve gotta get these stiffs off my land! ”
-
Arick Goomanovsky (@g00manoid) reported@awscloud It's worse than technical debt in one way - sprawl compounds through the connections, not just the count. Ten agents with no shared context or ownership isn't ten problems, it's every pair of them. The fix is a connective layer that makes them a network instead of scattered debt.
-
Ohm Patel (@Techieohm) reported“Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”
-
jayesh somani (@Jayesh_Somani_) reportedHey @awscloud I have lost access to the email id using which i have created an aws account and when i am trying to login with the id and password its redirecting us to reset passoword and the password is going to the email id which we have lost access here how can we solve this
-
Bob Tong (@bob80924) reported@Cloudflare @awscloud genuinely curious how tax/vat treatment works when your buyer is an anonymous agent wallet with no jurisdiction attached to it, feels like the accounting problem is way behind the payment rail problem right now
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport @AWSSupport Day 6. Production down. Same templated reply on Twitter, in the case, everywhere. If a multi-day production outage doesn't qualify for real escalation, what does? Asking someone with authority to review Case 178738643800497 and respond with an actual ETA.
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?
-
Sai Manikanta ☕ (@rebuiltWithSai) reportedDay 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic
-
Ümit Kaan Usta (@umitkaanusta) reported@AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1
-
Mr Sage (@GreatSage_0x) reportedCustos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon
-
Drama Memes (@drama_meme) reported@cgeorgiaw @AnthropicAI @awscloud Someone tell me why this is a hard problem and you can’t just do $ diff normal.genome sick.genome ? I am guessing it’s a statistical thing, but, if it were random then how would you figure out what’s different??
-
Brad (@beeradmoore) reported@QuinnyPig @awscloud I made a thing that posts in Slack when a new AZ goes live. It has pipped up twice in two days. I thought that was odd, it’s sat silent for so long and now twice in two days! Turns out it’s broken and will just repeat until I tell it that yes I know about eu-west-2d
-
Don KofiAdM1N 🎖️🎖️🎖️ (@DonKofiAdM1n) reported@anonymo6575 @AsakyGRN lol even a Jss2 can go all you just mentioned right now seriously you have no idea. Do you even know anything about Amazon aws javasscript c++ building a valid algorithm or a bank website that you login in with on your phone you think yahoo guys can do this ? lol your Knowledge is limited.
-
The Mediocre Inquisitor (@MediocreInqv2) reported@OpenAIDevs @awscloud I’m trying to buy a ChatGPT account on my work email and it’s not allowing me to. Will you be able to fix these issues? M trying to pay you
-
Hagop Chemedikian (@hagop17) reported@AWSSupport Account blocked — "not recognized as a valid account." Console login works, all resource creation fails. 10+ year old account, dormant for years, just resumed for a personal project. Three cases open, no response. Can someone look?
-
Sumedh More (@DroidBoyJr) reportedHey @awscloud @AWSSupport im trying Bedrock with root user and getting NOT_AUTHORISED error with 400. Tried support and the ai assistant couldn't find anything. Tried raising ticket, it asked me to upgrade support plan. Plan upgrade failing with error. Going nowhere #SOS
-
Swaroop Hegde (@SwaroopH) reportedTIL: @awscloud has been racking up ipv4 charges on an old test instance of mine even though it uses dynamic IP. Just checked that their launch wizard deployed new instances with the same issue without warning 🤷
-
Rami (@KingRomstar) reported@awscloud your multisession login doesn't even work right. I have to logout of one account and into another everytime I want to swap environments.
-
Corey Quinn (@QuinnyPig) reported@awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.