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	5 days ago
Pottstown	Website Down	10 days ago
Iztacalco	Website Down	13 days ago
Boca da Mata	Errors	25 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month 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:

• 
  Yuyun Francis (@FrancisYuyun) reported 5 minutes ago

  @AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."

• 
  jayesh somani (@Jayesh_Somani_) reported 8 minutes ago

  It's Sunday 11:30 AM. Production is down. Users can't login. My phone won't stop buzzing. Every tool I tried to use to fix it — blocked. AWS had quietly quarantined our only admin IAM user. Here's how I restored production in 2 hours without AWS Support @awscloud 🧵

• 
  Joy | 🔥 (@JoyKingdomx) reported 9 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.

• 
  Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported 12 minutes ago

  @awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!

• 
  Stephen “The Yellow Dart” Schutt (@schuttsm) reported 15 minutes ago

  @QuinnyPig @awscloud I get charged $0.55 every month. Fix that

• 
  Robat Das Orvi (@orvi_onethread) reported 17 minutes ago

  Does @awscloud have any real people in support? 😤 Frustrated after trying to reach a human for over an hour. Our server is completely down right now, and we can't get through. Terrible experience. We might finally have to switch away from AWS.

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

  @ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 23 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Babak (@bbkhbb) reported 24 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

• 
  Chintan Shah (@chintan86) reported 24 minutes ago

  @AWSSupport @awscloud Dues cleared, reinstatement requested — still waiting with no movement. My production workloads are down and every hour is costing us. Can someone please prioritise this? Case ID ready to share over DM.

• 
  Omni (@omnishredder_) reported 29 minutes ago

  @AmazonUK @Twitch @awscloud sort yo ****, I'm getting tired of ironically the last two days unable to watch twitch without lag or buffering at random with no explanation, it's almost like the ******* AI training is the problem that nobody wanted! How about ******* remove it!

• 
  ShenYubao (@ssybb1988) reported 29 minutes ago

  @AWSSupport @awscloudAWS 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

• 
  Zenwatts 🇺🇸 (@BullCall101) reported 31 minutes ago

  @awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.

• 
  Matt Lea (@schematical) reported 35 minutes ago

  @PhilipAnderse @awscloud @amazon What's the problem? I know a thing or two about AWS.

• 
  Siya (@reze_xqc) reported 40 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.

• 
  Priyanshu (@iproductAI) reported 41 minutes ago

  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.

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

  @QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?

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

• 
  Ümit Kaan Usta (@umitkaanusta) reported 47 minutes ago

  @AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1

• 
  Vera ¤⩊¤ (@VeraSimila) reported 47 minutes ago

  @awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak

• 
  Catalin C (@CatalinC_Uk) reported 50 minutes ago

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

• 
  Payal (@payal_codes) reported 55 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.

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

• 
  krrawn (@krrawn) reported 56 minutes ago

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

• 
  The AI Therapist (@TheAIShrink) reported 56 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

• 
  mark seery (@140ismymax) reported 58 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

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

• 
  Base Builder (@basedbuilder_io) reported 60 minutes ago

  What happens when agent payments go from "works on testnet" to "GA on AWS"? AgentCore Payments just shipped general availability via @awscloud and @CoinbaseDev. CDP Embedded Wallets handle the key material, x402 encodes the payment terms, and the whole thing runs as a single runtime-to-settlement flow on Base. No testnet disclaimer, no "coming soon" asterisk. The end-to-end shape: your agent detects a payable event, opens an x402 payment channel with the recipient, and settles in USDC through the embedded wallet, all without the user touching a key or approving a transaction. That's the runtime plumbing. What it unlocks is agents that can pay for services mid-execution without a human in the loop. API credits, inference time, data access, compute, whatever someone x402-wraps. The integration gotcha to watch is spending limit enforcement at the wallet layer. x402 handles the invoice generation and the payment terms, but the CDP embedded wallet's permissioning lives one layer up. If your agent holds a wallet with a default spend cap and then processes a batch of x402 invoices in sequence, the cumulative settlement can blow past the limit before the wallet context re-checks. The outcome is partial payment batches where some invoices clear and others bounce, and your error handling needs to know which ones landed. The dependent abstraction this pushes into focus is agent-to-rail routing: your agent picks a payment path based on cost, speed, and counterparty, not just a static USDC address. That's the next layer to wire.

• 
  Matthew (@OneShotCaller) reported 1 hour 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?)

• 
  Mr Sage (@GreatSage_0x) reported 1 hour 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