Amazon Web Services status: access issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Website Down (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Township of Evan	Sign in	11 days ago
Pottstown	Website Down	16 days ago
Iztacalco	Website Down	19 days ago
Boca da Mata	Errors	1 month ago
Township of Evan	Website Down	2 months ago
New York City	Website Down	2 months 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:

• 
  Brian Porter (@kbporter) reported 11 seconds ago

  @amazon @awscloud @AmazonHelp why do I have to continually contact you on social media for issues with your service? Why is your customer service online “help” so bad? $5 credits for delayed orders for a service we pay for is horrible!

• 
  Ohm Patel (@Techieohm) reported 1 minute ago

  “Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”

• 
  barney (@Southclaws) reported 2 minutes ago

  @jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors

• 
  WPBeginner (@wpbeginner) reported 6 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  Lori-Colorado (@lori_colorado) reported 7 minutes ago

  @marklevinshow The future, I bet: Giant Data—owner/consumers* long-term goal (5-10 years) Replace all of the servers in the AI data—mega center barns. Then they won’t need all these monster consumers of land, water, electricity. They will be empty silent mausoleums of AI’s startup period. * Meta, Open AI/Oracle, xAI, Microsoft, Amazon AWS, and Google. Reminds me of Jonathan Winters in The Loved One (1965) looking down from his helicopter over his empire of corporate cemeteries… “ I’ve gotta get these stiffs off my land! ”

• 
  Adel Bucetta (@adelbucetta) reported 7 minutes ago

  @Deeen_Codes @awscloud @devpost the real unlock here isn't just solving the hackathon prompt but figuring out what problems to automate first

• 
  Mohammed Nafees (@mnafees) reported 9 minutes ago

  yo @awscloud seems like a broken cert chain from your side

• 
  Brandon S (@BSaarX) reported 10 minutes ago

  @Gabby_Hoffman @awscloud Next you will say let them eat cake. 2024 was about mortgage rates getting lower and affordability. Now we see it was about crypto, AI and pushing data centers. What a let down

• 
  Nathan Den Herder (@natedenh) reported 10 minutes ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already

• 
  Corey Quinn (@QuinnyPig) reported 12 minutes ago

  @awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.

• 
  TechThought.org (@TechThought_org) reported 13 minutes ago

  An era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 14 minutes ago

  @jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 14 minutes ago

  @MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).

• 
  banhchung (@banhchugxanh) reported 17 minutes ago

  @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

• 
  Kenton Parton (@kenton_parton) reported 20 minutes ago

  Anyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?

• 
  Chris (@Mcatbeast) reported 25 minutes ago

  @awscloud has to have the worst sign-in page EVER. Every time I try to login as an IAM user it’s a complete headache and takes 30 minutes to figure out

• 
  Aqib Ansari (@Aqib_Ansari_) reported 29 minutes ago

  @AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 32 minutes ago

  @AWSSupport Thanks for your response and I've been keeping track for any updates very closely but the problem is these cases are either unassigned and if they are, no one is following up. I'm at the point of just giving up entirely cuz it's pointless waiting endlessly.

• 
  masaki (@silenthill_x) reported 35 minutes ago

  @AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 36 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Hannan (@truehannan) reported 39 minutes ago

  @AWSSupport Why AWS console is not opening? Its soo much slow even my internet and everything is fine. I used VPN too but nothing worked

• 
  Pixi Dust (@Bethco2257) reported 43 minutes ago

  @FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.

• 
  Matthew (@OneShotCaller) reported 43 minutes ago

  @ZZiata15569 @awscloud I have billing and budget alerts set up with AWS already. Main problem with a lot of tools I’ve used is too much noise in the alerts vs AWS option. Still, I think every AWS customer gets at least 1 surprise lol… part of initiation (onboarding?)

• 
  EJ Campbell (@ejc3) reported 47 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  kakafa.btc (@kakafa_btc) reported 50 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  The Trading Guy (@thetradingguy_) reported 51 minutes ago

  @AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?

• 
  Arian van Putten (@ProgrammerDude) reported 52 minutes ago

  @QuinnyPig @awscloud Are they gonna fix people needing to know what region their orgs IAM identity center is deployed in order to set up cli login? (How the heck would an employee know this??)

• 
  Jaimin Vaghani (@jaiminvaghani) reported 57 minutes ago

  @AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.

• 
  krrawn (@krrawn) reported 57 minutes ago

  I was wondering why @awscloud support was slow the other day

• 
  Yuliyan Tsvetkov (@yuli_tsvetkov) reported 58 minutes ago

  @per_arneng @awscloud That's the control plane handshake, not Terraform being slow. Don't put cluster create on the incident path. Keep a warm spare per env.