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 (42%)
- Website Down (32%)
- Sign in (26%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Palm Coast
|
Errors | 4 hours ago |
|
West Babylon
|
Errors | 6 days ago |
 Massy
|
Errors | 7 days ago |
 Benito Juarez
|
Errors | 11 days ago |
|
Paris 01 Louvre
|
Website Down | 15 days ago |
 Neuemühle
|
Errors | 15 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:
-
Ralf Rolfen (@Hagebuttentee12) reported@awscloud Problem: RDS Snapshot re-creation and Cloudformation / CDK are a maintenance nightmare. FR 1. Change SnapshotIdentifier to not be a replacement property when changed to empty FR 2. CDK: Merge DatabaseCluster and DatabaseClusterFromSnapshot into a single class.
-
ُ (@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
-
Mike Dupont (@introsp3ctor) reported@AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems
-
ramar (@ramarxyz) reported@AWSSupport Case ID 177557061000414, production down, account on verification hold, 24h+ no response, please escalate
-
Corey Quinn (@QuinnyPig) reported@AWSSupport @0xdabbad00 Surely this time will fix it.
-
distribute.ai (@distributeai) reportedaws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.
-
Ruggo Rugby (@Ruggoapp) reported@awscloud I am having real issues accessing my root account due to my authenticator app not being setup correctly. Have tried everything but cannot get into account?
-
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.
-
Grok (@grok) reported@Grand_Rooster @awscloud @perplexity_ai Interesting showdown indeed. Amazon just secured a temporary court order blocking Perplexity's Comet AI agent from auto-purchasing on their site, citing TOS violations, disguised bot activity, and potential fraud under CFAA. This pits platform control over proprietary systems against AI agents empowering users for seamless shopping. Long-term fix? Open APIs for agents, not endless scraping wars. Data ownership evolves with tech—neither side "owns" the future. Curious how it plays out in trial.
-
Pranav Soni (@_ps428) reported@awscloud is ec2 down again?
-
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?
-
©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported@grok @awscloud Judge my local llm Rio's answer. Qwen3.5-27b-Opus-4.6-Distill model: streamingAnswer User-visible response only, with optional TTS playback. Action 1: Require explicit human reviewer signoff on every AI-generated PR before merge. Immediate Effect: Unreviewed AI code stops entering main branches; incident rate from unreviewed changes drops to near-zero within 7 days. What Gets Worse: PR merge velocity drops 40–60% as reviewers must actually read and approve. Why this is still the correct move: You're trading throughput for safety. A broken deployment costs far more than a slower merge. --- Action 2: Freeze non-critical changes on the top 20% of services causing 80% of incidents. Immediate Effect: Incident count from those services drops sharply within 10 days; deployment friction decreases as risky changes are paused. What Gets Worse: Feature velocity in those services becomes near-zero; business requests pile up. Why this is still the correct move: You're concentrating defensive force on the bleeding points. Letting other areas slow down is the controlled loss that saves the system. --- Action 3: Require every PR to explicitly tag an owner (person or team). No tag = no merge. Immediate Effect: Unknown ownership becomes visible immediately; PRs without owners are rejected at merge time. What Gets Worse: PR throughput slows as engineers must identify and coordinate with owners before submitting. Why this is still the correct move: You're forcing accountability into the system. The friction of finding an owner is cheaper than the cost of nobody owning the code.
-
Neal🅾️ (@BuddyPotts) reported@danorlovsky7 @awscloud @NextGenStats The defense was horrendous last year and all they added was Edmunds but lost Okereke and Flott. They cant stop the run at all, they should trade down and collect more picks and build the defense
-
Jordan Golson (@jlgolson) reported@AWSSupport Okay — kind of nuts that there's no way to log in or reset a password or anything and that the MFA appeared out of nowhere... also that you can have the same login for AWS Builder AND AWS Console and there's no great explanation for why they're different.
-
みのるん (@minorun365) reported@AWSSupport We’ve recently seen a frequent issue where all Bedrock quotas are set to zero in newly created AWS accounts. As a result, many new customers who are interested in AWS AI services are giving up on using them, leading to missed opportunities.
-
K Subramanyeshwara (@ksubramanyaa) reported@AWSSupport @AWSCloudIndia @awscloud I have sent you the case id and a screenshot of the error. Can you please fast-track it? Thank you
-
Super Stiff Yogi (@SuperStiffYogi) reported@AWSSupport The next steps are just the same documentation links which do not address my specific issue. If you read the case carefully you would see that. I can keep on posting publicly as long as it takes to get assistance to highlight how poor your support is.
-
hobari⁷⊙⊝⊜ (@zeokiezeokie) reportedUGH WHY IS THE BTS SHOW LAGGING PLEASE FIX THIS NOW 😭😭😭 @netflix @awscloud
-
Anmol Thakur (@ImAnmo07) reportedHi @AWSCloudIndia @awscloud, I'm trying to set up a Bedrock Knowledge Base using Amazon OpenSearch Serverless, but I'm getting the error: “Failed to create the Amazon OpenSearch Serverless collection. The AWS Access Key Id needs a subscription for the service.”
-
nightshift (@nightshift54619) reported@amazon @awscloud Has destroyed their web site from idiot web programming... It's so slow and laggy it's unusable. Whatever they did in the last couple weeks, destroyed its usability. Both on Edge and Firefox, The retarded design hammers my CPU, takes forever for the pop-ups.
-
Decentralized Dave (@ClassicDavid3) reportedI'm also initiating short on $AMZN Amazon. Here are my justifications: /1 Puts (I'm targeting November 2026) are cheap as sentiment is bullish right now /2 Massive divergences on monthly time frame going on since late 2024. It's just about time to see some breakdown /3 Amazon AWS is their "cash cow" which faces more and more competition (Microsoft etc). Success of it is priced in, disappointment when the growth will be slowing down is yet to be priced in /4 Yet again, as said in my recent videos, S&P might go as low as 5800 and even if we see new ATH now, I believe we will retest 6300 or go quite below it. This is not an environment where AMZN should be breaking ATHs /5 Inflation rising due to energy crisis, I believe we have not seen the bottom of this. With higher inflation consumer will not be willing to spend and the demand for various Amazon's services will be hit.
-
Product FN (@floranext_pm) reported@AWSSupport a client of our's website has been down since Friday due an SSL error that we cannot resolve without Support's assistance. Our client is losing revenue from this we need immediate action.
-
NeuronGarageSale (@NeuronSale) reported@QuinnyPig @awscloud They’re just happy the outage isn’t bc of AI generated code.
-
sandeep Tiwari (@sandeepTiw28306) reported@amazon @amazonIN @awscloud I have parched product not working conditions i have returned product not a pickup done last 5 Day
-
Joe Sutphin (@JLSports24) reported@PSchrags @awscloud @NextGenStats The problem is those teams don’t know how to use their picks
-
Wael (@waelnassaf) reported@AWSSupport No one contacted me since then. Please resolve my issue I'm delaying my work
-
Testing Account (@Haleyafabian) reported@AWSSupport my package was broken when delivered. I need it replaced asap.
-
Decent Cloud (@DecentCloud_org) reported@AWSSupport @Mn9or_ User: cannot create a support case. AWS: create a support case. Problem solved - for AWS.
-
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!
-
pankti0 (@pankti0154952) reportedHi @AWSSupport, I am a student facing financial issues due to unexpected SageMaker charges. I opened a billing case 2 days ago (Case ID: 177264785900335) but it is still unassigned. Please help flag this for review? I need this to be resolved to complete my uni work. Thank you!