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.
- Errors (37%)
- Website Down (34%)
- Sign in (29%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Glendale
|
Website Down | 1 day ago |
|
Oakland
|
Sign in | 3 days ago |
 Greater Noida
|
Errors | 3 days ago |
|
Alamogordo
|
Website Down | 8 days ago |
|
San Francisco
|
Website Down | 10 days ago |
|
Mercersburg
|
Sign in | 12 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:
-
chen (@chen10075495) reported@awscloud Amazon AI Pricing Is Killing the Buy Box Losing Buy Box because AI compares my product to cheaper, non-equivalent listings — even external ones. To compete = sell at a loss. This punishes real brands. Fix this. #AmazonSeller
-
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.
-
Decent Cloud (@DecentCloud_org) reported@Mn9or_ @AWSSupport No support subscription means you wait for someone else's ticket to fix your outage
-
Vinit Taneja (@vinit_taneja) reported@amazonIN @awscloud @JioHotstar I got the tech help from a group of movie buffs. The problem originated because of a glitch at your end. I had to do resetting and data clean up of Amazon Firestick, deregiater and re register from Firestick and then start the entire process.
-
Aman (@itsreal_aman) reported@AWSSupport My AWS Account got hacked, someone has changed my root email address I have MFA and my root email them also someone has updated the email now I am unable to login my account
-
Henrique Lima (@HenriqueLi88059) reported@AWSSupport @awscloud Our medical imaging platform has been DOWN for 24+ hours. Real patients. Real exams. Real impact. AWS suspended with ZERO explanation and ZERO contact after opening. This is a Radiology/PACS system. Every hour matters. We are desperate for a response.
-
Dhananjay Maurya (@dhananjaym182) reported@AWSSupport I have sent Aws case in private message please have look and fix the issue
-
Rahul Khatri (@Rahulk644) reported@AWSSupport. Trying to resolve a $200 billing from accidentally left-on resources after our student startup shut down. I've had 2 cases open requesting a waiver & account closure, but both have sat unassigned for 1 month. Need urgent help. Cases: 177520122800121 177591632700789
-
Trevor Skinner (@PrometheusAIsec) reportedI’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.
-
Woods (@RyanRael16) reported@Midnight_Captl The irony is genuinely remarkable. Every hyperscaler on earth confirms they cannot build infrastructure fast enough. Azure supply constrained at 40% growth. Meta raising capex to $145B. Amazon AWS growing 28% with no signs of slowdown. Google Cloud up 63%. All four saying they need more chips faster than anyone can deliver them. And Nvidia is down 4%. The only rational explanation is the market is pricing in custom silicon risk. If Microsoft, Meta, and Google are all building their own chips to supplement GPU supply the fear is Nvidia's pricing power erodes over time even as demand grows. That is a legitimate long term concern dressed up as a short term sell. But in the near term supply constrained hyperscalers raising capex is the single most bullish data point for Nvidia that exists. The market will figure that out. It usually does. Just not on the same day.
-
Wat (@WatTuiteg) reported@awscloud So dont buy Hyundai because you wont own the car, will have AI and and you wont be able to fix or tinker with it, only authorized dealers that will charge you thousands to update a firmware. NAH
-
manish (@mjha2088) reported@AWSSupport Thank you! The entire db.r7i family shows reduced vCPUs for SQL Server & Oracle vs MySQL/PostgreSQL/Aurora in console. The docs page has no mention of this engine-specific difference — undocumented and critical for licensed engine customers planning costs.
-
Jason Hall Jr (@JasonHallJr2) reported@NBA @awscloud This just shows he isnt the problem with the rockets
-
dani (@danisconverse) reported@awscloud @amazon I'm writing to report a clear case of animal cruelty by an Amazon delivery driver in Rathdrum, Idaho. On around April 5, 2026, the driver grabbed Joe Hickey's small dog, Rocky, by the neck and slammed him onto rocks, causing broken bones and $10,000 in vet bills
-
Hershal Dinkar Rao (@Hershal0_0) reported@awscloud @PGATOUR still won't help me fix my slice though
-
Bryan (@0xp4ck3t) reported@AWSSupport URGENT - 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
-
David Mauas (@dmauas) reported@awscloud why, WHY don't you fix the web console UI/UX?! AWS console seems to actually try to suck! It gets WORSE with time! Actually using bash is better than the disgusting web console!
-
XXX (@MshenguMasia) reported@Mikedotcoza His offer is insulting to the RSA community. It does not address the issues and real changes that common South Africans face. Others invest, such as the Amazon AWS project and Microsoft. He wants to talk like people really don't have access to the internet, as if it's a bigger
-
James Baldwin (@TwistedEdge) reportedI *really* want to like AgentCore but the more I build with it and run into limitations, the more I worry it's still too early. @awscloud. First I run into DCR issues with a custom MCP and now it seems AgentCore doesn't pass ui:// resource requests through.
-
Roberto Shenanigans (@Rob_Shenanigans) reported@PSchrags @awscloud @NextGenStats Hard disagree that there's no hole currently at LT. Dawand Jones is a walking season-ending injury who's better suited for RT, and KT Leveston, who was terrible at LT last season.
-
yourclouddude (@yourclouddude) reportedA startup wasted $50K on AWS. Not because AWS is expensive- because they didn’t understand it. Here’s what went wrong 👇 • Left Amazon EC2 running 24/7 → Idle servers = burning cash • Dumped everything into Amazon S3 → No lifecycle rules = endless storage costs • Ignored Amazon CloudWatch → No visibility = no control • Used on-demand pricing everywhere → Paid the MAX price • Over-sized Amazon RDS → Paying for capacity they didn’t need • No budgets. No alerts. No limits. → Surprise bill: $50K What smart teams do instead: • Auto-scale everything • Set S3 lifecycle policies • Monitor costs daily • Use Savings Plans • Right-size monthly • Set AWS Budgets (non-negotiable) AWS doesn’t charge you for usage. It charges you for mistakes. Fix this early → save thousands 💸
-
Perfect Enemy (@PerfectEnemy376) reported@AWSSupport I sent support requests two weeks ago, but there is still no solution to my issue! My problem is being completely ignored!
-
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
-
Hetarth Chopra (@HetarthVader) reported@orangerouter and I spent days debugging why our inter-node bandwidth on @awscloud was slow. 8x A100 TP8PP2 serving across machines. bandwidth was ~100 Gbps. should have been 400 Gbps.
-
The Night King (@nightkingog) reportedI am witnessing @awscloud is doubling down
-
Ronny A. (@DjTimbao) reported@AWSSupport The issue is that the team is NOT responding via the case. It’s been 3 days for this one and 8 days for the previous one. I am totally blocked. Can you at least escalate Case ID 177654556500245 to the Billing and account team? 'Working via the case' is currently impossible Thanks
-
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.
-
FortuneFavorsTheBold (@BeBoldAlways) reported@PSchrags @awscloud @NextGenStats Not a bad summary but KC failed to draft any OL help which needs addressing. One of their front five guys goes down w/injury? Trouble.
-
Kaspa Mode: ON (@KasConviction) reported@cryptorover Ethereum is not even fully decentralized. No PoS can be with much of the node control on Amazon AWS. ETH is slow, expensive, and not fully decentralized.
-
canadianbreaches (@canadabreaches) reportedBREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.