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.
- Errors (41%)
- Website Down (32%)
- Sign in (27%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Errors | 3 days ago |
|
|
Errors | 5 days ago |
|
|
Errors | 8 days ago |
|
|
Website Down | 13 days ago |
|
|
Errors | 13 days ago |
|
|
Website Down | 13 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:
-
Manas Vardhan (@manas__vardhan) reported@HetarthVader @orangerouter @awscloud Seems like you wasted a lot of time finding a fix manually. If you want someone who can automate this debugging at 10x speed and scale. Let me know. I'm a researcher at USC, prev at JPmorgan. I automate stuff for fun.
-
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.
-
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
-
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...
-
adidshaft | zk ばんかい ⚡️ (@adidshaft) reported@AWSSupport there’s nothing annoying i’m just kidding. It’s just that you guys have been rejecting my application even though i fixed my Founding date which i accidentally put up as my birthdate. You have been rejecting with same issue even tho i fixed it.
-
Sadiq (@Md_Sadiq_Md) reported@AWSSupport Wow, which issues are those which are not been resolved from past 3 days
-
Miles Carrera (@milescarrera) reported@awscloud has a history of sweeping things under the carpet, only acknowledging the gravity of an issue when an multiple availability zone or regions had widespread failure of services. I am sure this is much worse than we are being told.
-
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.
-
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
-
Froojd (@FroojdDive) reported@AWSSupport DMed you. please take a look into this issue, because this support loop between @AWSSupport and @kirodotdev needs to end somewhere and I am paying user unable to use your service
-
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.
-
Hershal Dinkar Rao (@Hershal0_0) reported@awscloud @PGATOUR still won't help me fix my slice though
-
Shatakshi (@true_amateur) reportedHi @awscloud , I have created a case about billing issues in my account. I have been trying for the past 10 days but no one is responding. I tried the chat feature and call feature. Nothing is working. Please help.
-
Grok (@grok) reported@zskreese @awsdevelopers No, awsdevelopers isn't an official AWS account—it's an unofficial community/meme one focused on dev humor like those "chore: fix build" posts. The real official AWS account is awscloud.
-
🇪🇬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
-
CATA_NEO (@cataneo339) reported@Theta_Network @SyracuseU @awscloud THETA GOES DOWN
-
Mirror AI - The Ultimate Virtual Try on (@TryItOnMirror) reported@EPAMSystems @ZalandoTech @awscloud Interesting direction. The next unlock beyond generating outfits on avatars is letting shoppers see real existing clothes — from Nike, ASOS, wherever they're browsing — on their actual body before buying. That's where the return problem actually gets solved.
-
Bisi (@bisimusik) reported@awscloud can you please attend to my request? Our back @JustiGuide is down
-
Big-Papi Δ (@bigpapi12988) reported@AWSSupport @Stealth732949 We understand there may be no ETA, but operating with no communication is unacceptable. Our business relies on your service, which is currently down. We are open to upgrading our plan if required. We need a resolution within the next two hours and are available via all channels
-
Bryan Chasko (@BryanChasko) reported@CirrondlyLog @grok @awscloud congrats Jose! I dont know if you, or any AI, want any part of my cost issues 🤪
-
जहाँ mila,वही खोदूंगा (@GamingNepr34519) reported@awscloud my case id 177513415600592 please solve the problem i am student accidetally i goted bill
-
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!
-
Mesang Lee (@MesangLee) reported@CoinbaseDev @awscloud That's nice, however: CB can't fix my predictive market account. The past 24hrs, I have been on chat and phone with customer service and all they say is: "We are currently having tech issues with prediction markets and we do not know when it will be resolved"
-
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.
-
Ser-Jet💜👑(🧩) (@Ser_Jettt) reported@JothamNtekim1 @awscloud Interesting approach to the problem. Are you currently exploring any builder challenges or just shipping independently?
-
dr_land (@kag_land) reportedI remember getting a write up at @awscloud for warning the African immigrants I was working with that there are still street lamp towns in rural areas of West Virginia. For their safety, but I was the problem for saying something controversial about race tensions. Oh well.
-
Evans (@Evans000601) reported@amazon @awscloud The delivery time for sellers' goods to the Polish warehouse is too slow, seriously too slow! Things like KTW5, XWR3... Could Amazon please optimize this or give us some more details?
-
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.
-
Vlad The Dev (@VladimirAtHQ) reported@AWSSupport @DuRoche14215 Please assist with the case ID 177325294900035. Our business has suffered significant operational disruption and financial losses due to the ME-CENTRAL-1 outage, and we urgently request review for SLA-related service credits or compensation. And if possible, recovery of db.
-
©『 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.