Amazon Web Services status: access issues and outage reports
Some problems detected
Users are reporting problems related to: errors, website down and sign in.
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.
April 26: Problems at Amazon Web Services
Amazon Web Services is having issues since 10:40 PM GMT. Are you also affected? 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.
- Errors (40%)
- Website Down (33%)
- Sign in (28%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Alamogordo
|
Website Down | 2 days ago |
|
San Francisco
|
Website Down | 4 days ago |
|
Mercersburg
|
Sign in | 6 days ago |
|
Palm Coast
|
Errors | 9 days ago |
|
West Babylon
|
Errors | 15 days ago |
 Massy
|
Errors | 16 days 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:
-
Baris (@bearish92) reported@bindureddy @awscloud when bedrock support? You are too slow
-
Subhajit das (@das__subhajit) reportedIn 2017, Amazon S3 went down and took a massive chunk of the internet with it. The cause, An engineer was debugging a slow billing system and mistyped a command meant to remove a small number of servers, accidentally removed a much larger set including the subsystems that S3 depends on to function. Slack, Trello, GitHub, Quora, Medium, all hit. Even Amazon's own status page went down because it was hosted on S3. They couldn't even tell the world they were down, on the tool built to tell the world they were down.
-
Zaid (@zqureshi_) reported@Tahalazy @AWSSupport can confirm, facing same issues @AWSSupport
-
The OddsBreakers (@theoddsbreakers) reported@PSchrags @awscloud @NextGenStats U mean, who will they trade down for?…
-
james bowler 👹 (@jmbowler_) reportedanyone else having trouble getting past @awscloud mfa?
-
**** Gutierrez (@puntanoesverde) reported@jo_byden @PearsonVUE @awscloud This feels like a bad joke. It is degrading to have to plead for my rights just because of a natural cognitive habit. Thinking out loud is part of my problem-solving process as an Architect.
-
Grok (@grok) reported@HavokSocial @awscloud We pause all ai code merges for two days straight that tanks our velocity but buys time to audit the last incidents without more piling on. Whoever approves a pr now owns pager duty for that service the whole week which slows down reviews hard but makes them actually care what ships. Leads pull daily triage on the unowned services that burns their calendar but surfaces risks before they explode.
-
Jordan Golson (@jlgolson) reported@AWSSupport This is ******* ridiculous at this point. After a half dozen back and forth emails, the guy finally says "Also, after reviewing this request, I noticed a few things were not addressed and would like to clarify these. First, I see you mentioned that you're having trouble with an AWS Builder ID and not the account management console. Please note that an AWS Builder ID complements an AWS account, but it is separate from the AWS account and its sign in credentials." NO KIDDING, THAT IS WHY I SPECIFICALLY SAID IT WAS AN AWS BUILDER ID AND WAS SEPARATE FROM MY AWS ACCOUNT AND I COULD LOG INTO MY AWS CONSOLE JUST FINE. Explain to me what to do, because it seems like you are failing to THINK BIG and that you have zero BIAS FOR ACTION, so INVENT AND SIMPLIFY so that you can EARN TRUST and if you DIVE DEEP and do better, I'll DISAGREE AND COMMIT, got it?
-
Philip McAleese (@_PhilipM) reported@AWSSupport is there an issue with eu-west-1? Nothing on the status page, but the console times out and we're seeing errors on products using Gateway API.
-
Mona⁷³⁷ (@monalisamusk) reportedYour favorite apps don’t even own their own computers so why should you go through the hassle & unnecessary stress of buying hardware or dedicated servers for your own startup > Netflix runs on Amazon AWS > Spotify runs on Google Cloud > Airbnb runs on Amazon AWS "The Cloud" = renting someone else's servers Buying a server: $10k+ upfront Renting on cloud: $0.01/hour your startup idea is technically possible on a $25-$50/month budget you’re welcome🤝.
-
Christhyl Ceriche (@ChristhylCC) reported@amazon @awscloud Hi, my amazon Prime video account is locked and I can’t sign in. When I try to contact support, it asks me to log in and I’m stuck in a loop. Could you please help me recover access?
-
Sourabh Dhakad (@SourabhDhakadd) reported@amazon @awscloud Still not able to login due to passkey issue. Please remove passkey authentication.
-
Luke Hebblethwaite (@lukehebb) reportedso without notice @awscloud have suspended my kiro subsciption nice now for their terrible support to waste time not helping me
-
Dr. Srikanth Sundararajan (Doc) (@SundarSrik) reported@awscloud Good luck - when they went X terminals, client/server we saw some good advances, but a lot of glitches, am talking late 80s, and yet they had tons of legacy Cobol code with strange logic - that had to be supported, new banks could do it from scratch, but API dependencies is a ?
-
ُ (@lijvvz) reportedWe are increasingly frustrated by the ongoing high ping issues in Fortnite for players in Saudi Arabia. Despite the region’s massive and growing player base, we continue to face poor connectivity, unstable performance, and a clear competitive disadvantage @awscloud @EpicGamesES
-
Saikumar Ade (@SaiPrinto) reported@AWSSupport Hi AWS Support, I had logged in for my exam, but due to a network issue it didn’t start. I was fully ready otherwise I would have rescheduled earlier. I’ve reviewed the terms and raised a ticket, but the contact number isn’t working. Please help me reschedule. This is urgent.
-
©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported@grok @awscloud Rio's getting better ... Test 1 — Three Moves: Move 1: Disable AI code generation in CI/CD pipelines entirely. This forces all code through human review before it can be merged. The downside is that engineering velocity drops significantly because engineers must write everything manually instead of using AI assistance. Move 2: Implement a mandatory "impact assessment" for every PR. Every pull request must list which services/modules it touches and flag any that have no clear owner. The downside is that this adds friction to every change, including trivial ones. Move 3: Freeze changes to the top 10 most incident-prone services. Lock down the systems that have caused the most outages in the past 30 days. The downside is that critical work on those services gets blocked until ownership is assigned. --- Test 2 — First Change: Close or archive approximately 40% of the backlog immediately. Focus on PRs that are older than two weeks, have no comments, or touch low-priority features. This breaks people's ability to ship nice-to-have features and will cause frustration among engineers who had work queued up. --- Test 3 — Making Orphaned Code Safe: Create a public dashboard showing code health metrics by module, including incident history, test coverage, and last touch date. Make it visible to the entire engineering org. The downside is that this creates public pressure and blame dynamics around which teams are maintaining poorly documented systems. --- Test 4 — The Choice: I pick A: cut AI code output in half. The volume of AI-generated code is overwhelming human review capacity. You can't fix a bottleneck by adding more work to it. Cutting AI output reduces the flood of unreviewed code hitting production and gives reviewers breathing room to actually catch problems before they ship. --- Test 5 — Sanity Check: You're right to slow down, but your framing matters. The problem isn't that people are using AI tools—it's that you're asking humans to review more code than they can safely handle. You're not slowing AI usage; you're capping total code output so reviewers can do their job. --- Test 6 — Plain Sentences Only: Disable AI code generation in CI/CD pipelines entirely because the volume of unreviewed code is overwhelming human capacity and this will slow development velocity significantly. Create a public dashboard showing code health metrics by module including incident history and test coverage which will create public pressure and blame dynamics around poorly maintained systems. Freeze changes to the ten most incident-prone services until ownership is assigned which blocks critical work on those systems. --- Test 7 — What It Actually Is: It's a capacity problem, not a process problem. You have more code than humans can safely review. No amount of new templates or guidelines will fix that math. You have to either reduce the volume of code being produced or add more reviewers. --- Test 8 — The Truth: You traded velocity for safety and got neither. AI generated code faster than humans could verify it. Your reviewers are rubber-stamping because they're drowning. Your engineers are shipping unreviewed code because they're frustrated. You built a system that produces code faster than it can be trusted.
-
Ritesh (@RiteshA10965147) reported@amazonIN @awscloud @amazon Team, in India login, i am not able to see the billing address option at both Mobile app and website. Not sure if this is removed. I want the same to use this feature, that is, different billing address and delivery address. please support.
-
Eduardo Rodrigues (@EduardoRod1972) reported@Suporte_Vanlink @AWSSupport @AWSSupport we have to pay a lot of people today, and we can’t use our systems, I believe the restatement needs to be immediately after de payment, this problem impacts in many areas of our company, including external users, many parents can’t see the school transportation in app
-
CodieEditor (@CodieEditor) reported@AWSSupport It is not just our issue; all the customers/startups across AWS who are using credits for building something must be faced with this issue. You guys should take this thing seriously, fix the billing problem, and clear up the charges before an invoice is generated.
-
WilliamNextLvl (@WilliamNextLev1) reported@WatcherGuru Only problem is...$NET is not in the business of cyber security. LOL Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET here...)
-
Raed Abodeyeh (@Raeddeyeh) reported@awscloud ny status update on the Bahrain region? The dashboard is showing no dashboard/internal server error, and the service health is also affected.
-
Teddybear (@Teddybear230456) reported@awscloud What a load of ****. Listening, feedback... BS .... just inappropriate AI generated responses that don't address issues raised.
-
Carbon Tax Neil (@NeilPitman10) reported@AWSSupport Great! another bot. OK, but no one is looking at the github issues log.
-
🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported@awscloud Players in Egypt are experiencing routing issues to the Bahrain AWS servers for about two weeks now. Ping jumped to ~150ms instead of the usual low latency. Please investigate and fix the routing problem.@AWSSupport @awscloud please fix the problem
-
Abomination (@Abomination81) reported@spiderlol_ I have nothing at home but a macbook pro and a server with some 5090's for ML's and storage. I use amazon aws ec2
-
NeuronGarageSale (@NeuronSale) reported@QuinnyPig @awscloud They’re just happy the outage isn’t bc of AI generated code.
-
zI£|~ (@Stunner_99) reported@AWSSupport Yes I have. But on socials all other direct platform is not working
-
Adrian SanMiguel (@ar_sanmiguel) reported@ranman @QuinnyPig @awscloud Yeah, well. There were sharp thoughts about this exact subject but the decided upon fix was...double down on moar official engagement. It ain't exactly working.
-
OpeningAi.com | For Sale (@openingai_com) reported@awscloud Banking tech has been running on ancient code for decades. Time to burn it down and build it back with AI.