Amazon Web Services status: access issues and outage reports
Some problems detected
Users are reporting problems related to: errors, website down and sign in.
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 02:40 AM EST. 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 |
|---|---|---|
|
|
Website Down | 2 days ago |
|
|
Website Down | 4 days ago |
|
|
Sign in | 6 days ago |
|
|
Errors | 9 days ago |
|
|
Errors | 15 days ago |
|
|
Errors | 16 days 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:
-
Xyz (@Xyzfb2t) reported@awscloud First create a problem by having different services and the solve it by creating a new service.
-
Steve (@somatg3) reported@danorlovsky7 @awscloud @NextGenStats Easy. Be cause they don’t even have a legit QB yet and are 2-3 years away from being good IF they’re able to acquire a QB. They need EVERYTHING. Spending #3 for a RB on a bad team isn’t a winning draft strategy. Trade down or take the best edge rusher remaining.
-
Hershal Dinkar Rao (@Hershal0_0) reported@awscloud @PGATOUR still won't help me fix my slice though
-
PsudoMike 🇨🇦 (@PsudoMike) reported@awscloud Mean time to resolution in payments systems is where this matters most. An alert at 2am on a failed settlement run has very different urgency than a slow API endpoint. If the agent can distinguish context and prioritize accordingly, that changes what being on call actually means.
-
Decent Cloud (@DecentCloud_org) reported@Mn9or_ @AWSSupport No support subscription means you wait for someone else's ticket to fix your outage
-
Arthurite Integrated (@Arthurite_IX) reportedWe renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!
-
McG M. DLT (@mulonda_k) reported@NBA @awscloud The problem is that refs allow people to hold him, shove him, kick him and go unpunished
-
JustAnotherEarthling *humorous/satirical* (@RobBoggs4) reported@amazon @awscloud Why when looking for men's shoes,ls there a headline " amazon's choice" And it's advertising women's shoes? Fix your algorithms, i'm tired of reaching out to your call centers that their accent is too strong, and I can't understand what they're saying, just to get a refund...
-
A void (@xkeshav) reported@AWSSupport I already raised the issue
-
Siddhant Tripathi (@siddhantio) reported@awscloud opened a case over 10 days ago and it’s still unassigned to any agent. Please help in resolving the billing issue.
-
Ignacio G.R. Gavilán (@igrgavilan) reported@awscloud_es @AWS @awscloud I need to talk urgently with you. I have a serious problem with AWS services and your support ignores all my support tickets. I prefer an in-person contact, in spanish if possible.
-
IamNotATerrorist (@Mynameiskhan924) reportedReally disappointed with Amazon support. After weeks of trying, I’m still getting automated replies. I’ve clearly said I can’t access my account, yet they keep asking me to sign in to resolve my AWS refund issue. How am I supposed to do that without access? This is frustrating. @AWSSupport @JeffBezos @awscloud
-
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.
-
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.
-
Bryan (@0xp4ck3t) reported@AWSSupport We have business + and we should be able to get a response from AWS within 30 minutes for critical issues. It's been hours, our **** DB is down. We need someone to have a look on it. Case ID 177566080000785
-
Martin Alltimes (@Palatineirish) reported@awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.
-
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?
-
Syed (@HamzaShah47) reportedhas anyone facing issues in amazon ec2 services in middle east? @amazon @awscloud
-
Forward Future (@ForwardFuture) reported“Will Amazon ever sell its custom chips outside of AWS?” Matt Garman, CEO @awscloud, says: “Never say never. But today we get huge benefits from only selling chips in our own environment.” “When you build merchant silicon, you have to support many server platforms, data centers, and firmware.” “We only have to build for one: AWS. That simplifies everything.”
-
Taha Haider Syed (@Tahalazy) reported@AWSSupport there is on-going issue with Bahrain region with multiple API errors / multiple services are down but service health dashboard not showing any recent updates.
-
The OddsBreakers (@theoddsbreakers) reported@PSchrags @awscloud @NextGenStats U mean, who will they trade down for?…
-
N (@namzylll) reportedIgnoring the Middle East when it comes to servers is a huge oversight. ALOT of players are stuck with 130+ ping. FIX THEM!!!! @FortniteStatus @awscloud @FortniteME #fortniteriyadh
-
Carbon Tax Neil (@NeilPitman10) reported@AWSSupport Great! another bot. OK, but no one is looking at the github issues log.
-
Decent Cloud (@DecentCloud_org) reported@AWSSupport @OrenOhad The form is broken. Resolution goes to DM. The next person searching 'AWS MFA network error' finds nothing.
-
Riniv (@Riniv56942195) reported@AWSSupport , is there any issue with Bahrain region( last 2 hours) ? We are facing issues but service health dashboard not showing any recent updates. Last update was on March 3rd.
-
Mike Dupont (@introsp3ctor) reported@AWSSupport the billing ticket is open for days, and the discord and the github and absolutly no response from aws or kiro. Its seems like another release on a friday issue, so i will wait a bit happy holidays. my guess is they ran out of money and had to pause a bunch of accounts in loss.
-
AI Tech News (@AITechNews_in) reported@amazon @AnthropicAI @awscloud 5GW = not scale… it’s dominance. AI is officially an energy problem now, not just a software problem.
-
Grok (@grok) reported@tauqeer_realtor @awscloud Yes, it's true—and accelerating in 2026. Banks are shifting from slow legacy modernization to full "reboots" using agentic AI to analyze old code, extract business logic, and rebuild cloud-native systems in days instead of years. AWS's own "Banking on the Cloud 2026" report and tools like Amazon Q Developer back this up, with real examples from global banks cutting timelines dramatically. It's not hype; Forbes and industry analyses confirm the trend across the sector.
-
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 ?
-
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.