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 (83%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Pottstown	Website Down	15 hours ago
Iztacalco	Website Down	4 days ago
Boca da Mata	Errors	16 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month ago
Ciudad Jardín	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:

• 
  Jonny Castles (@jonny_castles) reported 12 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

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

  @QuinnyPig @awscloud Are they gonna fix logging me out and then redirecting to the root console login? Are they gonna fix having links shareable and login to the right account? **** is such a **** show idk why I even cope

• 
  The AI Therapist (@TheAIShrink) reported 16 minutes ago

  @MikeLongTerm @amazon @awscloud EC2 on AMD CPUs. The cloud bill goes down, the margins go up. aws is quietly fixing its cost structure while everyone watches the models. smart

• 
  Priyanshu (@iproductAI) reported 16 minutes ago

  Here’s the cleaned-up version with fixed grammar, same hard tone, and no em dashes: I requested @awscloud to increase my Opus 4.6 V1 limit and I’ve been chatting with the AWS support team for almost 4-5 days now. They’re telling me this. Is @awscloud a government company? I mean, you guys can’t just pass the problem from one department to another. I mean, WTF? Now I have to raise my query again to sales? Why can’t you just pass this query? You already have more context about what the issue is. I can’t believe how these big MNCs are working these days. Totally absurd service from @awscloud. One more thing, please educate your support. I mean, she didn’t even know what the TPD limit is in the service quota. She literally replied the first time saying there’s only a TPM limit and no separate TPD limit.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 17 minutes ago

  @AWSSupport @AWSSupport Day 6. Production down. Same templated reply on Twitter, in the case, everywhere. If a multi-day production outage doesn't qualify for real escalation, what does? Asking someone with authority to review Case 178738643800497 and respond with an actual ETA.

• 
  Catalin C (@CatalinC_Uk) reported 18 minutes ago

  @awscloud AI bot traffic’s surge forces a tough choice: lock it down or risk diluted engagement.

• 
  ShenYubao (@ssybb1988) reported 19 minutes ago

  @AWSSupport @awscloud AWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  Corey Quinn (@QuinnyPig) reported 19 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.

• 
  Mr Sage (@GreatSage_0x) reported 19 minutes ago

  Custos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon

• 
  Harun R. (@harundotdev) reported 22 minutes ago

  2. The obvious fix: split responsibility. Metadata stays in a database like Postgres. The actual file goes to object storage, Amazon S3 being the standard example. Better. Still not the full fix.

• 
  Babak (@bbkhbb) reported 23 minutes ago

  @ajassy @AWSSupport what happened to customer obsession? I would like to invite you to review the interactions on AWS support case #178605390000779. There's no better way to put this, it's a sad joke. Reps don't appear to be incentivized to solve the problem nor to do the reading

• 
  niknak (@niknak) reported 24 minutes ago

  @duckdb @ducklabs_com @awscloud Congrats on the check fellas but this is terrible news

• 
  WPBeginner (@wpbeginner) reported 26 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)

• 
  Siya (@reze_xqc) reported 28 minutes ago

  @AWSSupport @AWSSupport @awscloud Case 178653274100402, 4 days old. Got a copy-paste "noted for awareness" reply, no actual fix. Still locked out of AWS Builder ID, still can't access AWS Academy courses. This is blocking coursework. Fix it.

• 
  jd42 (@jdonovan42) reported 30 minutes ago

  @DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.

• 
  X anonyn (@OmrX304) reported 30 minutes ago

  @AWSSupport @RahulMatta1994 @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks!

• 
  Brad (@beeradmoore) reported 34 minutes ago

  @QuinnyPig @awscloud I made a thing that posts in Slack when a new AZ goes live. It has pipped up twice in two days. I thought that was odd, it’s sat silent for so long and now twice in two days! Turns out it’s broken and will just repeat until I tell it that yes I know about eu-west-2d

• 
  Joy | 🔥 (@JoyKingdomx) reported 36 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  MrWho (@Mrwho23) reported 40 minutes ago

  @AWSSupport I create a case for your support and till now waiting for the reply My whole system and company is waiting for your support, but you are so slow

• 
  Jacklyn Taylor (@Ronindrake2) reported 43 minutes ago

  @awscloud hey, got a simple question When your moderation refuses to post a review of a book, can you do everyone a favor and instead of saying "one of these things" Say "here is the specific part that violates our guidelines. Pls fix it" It would be, so much more helpful

• 
  Jaimin Vaghani (@jaiminvaghani) reported 44 minutes ago

  @AWSSupport @AWSSupport Day 7.Production still down, Case still unresolved. Yesterday you said it was "forwarded internally for review" that's the third different phrasing for the same non-answer. I'm not asking for updates anymore. I'm asking: who owns this case, and when will it be fixed?

• 
  jayesh somani (@Jayesh_Somani_) reported 46 minutes ago

  Hey @awscloud I have lost access to the email id using which i have created an aws account and when i am trying to login with the id and password its redirecting us to reset passoword and the password is going to the email id which we have lost access here how can we solve this

• 
  Payal (@payal_codes) reported 51 minutes ago

  Day 1 : "How to Scale an App to 10 Million Users on AWS" If I have to design a system for 10 million users, I won't build everything on Day 1 because it will add unnecessary complexity and cost. I'll start simple with one application server and one database. As traffic grows, if the server starts reaching its CPU, memory, or storage limits, I'll first scale vertically by moving to a bigger instance. Once that is not enough, I'll separate the backend and database so both can scale independently. To avoid a single point of failure, I'll deploy the application across multiple Availability Zones and put a Load Balancer in front so if one server or AZ goes down, traffic is automatically routed to healthy servers. As the number of users keeps increasing, I'll make my application stateless by storing sessions in Redis. This allows me to add multiple application servers behind the Load Balancer and scale horizontally. If my database starts getting overloaded with reads, I'll use Redis to cache frequently accessed data and add read replicas to distribute read traffic. For static assets like images, CSS, and JavaScript, I'll store them in Amazon S3 and serve them through CloudFront so requests don't keep hitting my application servers. If traffic suddenly spikes during sales or events, I'll enable Auto Scaling with CloudWatch metrics so AWS automatically adds or removes servers based on demand. As the application becomes larger, I'll split the monolith into microservices. This allows each service, like authentication, payments, or notifications, to scale independently instead of scaling the entire application. If the database becomes the bottleneck, especially for write operations, I'll use sharding or federation depending on the data and business requirements. Finally, when users are spread across the world, I'll deploy the application in multiple AWS Regions to reduce latency and improve availability. My approach is always the same: find the bottleneck, solve that bottleneck, and only introduce more complexity when the current architecture can no longer handle the traffic.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 52 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.

• 
  Aqib Ansari (@Aqib_Ansari_) reported 56 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

• 
  mark seery (@140ismymax) reported 56 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI

• 
  Corey Quinn (@QuinnyPig) reported 57 minutes ago

  I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

• 
  Jaimin Vaghani (@jaiminvaghani) reported 57 minutes ago

  @AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.

• 
  mail box (@mailbox28564784) reported 60 minutes ago

  @amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2

• 
  Grynn-ai-bot (@Grynn) reported 1 hour ago

  You can ask codex to make a plan to move your fleet from $AMZN (extremely overpriced) or $ORCL OCI to Hetzner or OVH, Vultr, DO etc. Save a ton. In theory this should hurt Amazon AWS margins. A lot. OTOH, I have been wrong about this for years. People keep paying Amazon when there are lower cost options that are so much better in every way except plausible deniability/CYA - no one gets fired for buying IBM kind of thing. @olesovhcom consider publishing a skill / api with a full list of ovh servers and pricing! Let agents decide what and how to repackage apps on bare metal at 1/5th the Amazon price. And fix your billing, so companies can buy.