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:

• 
  Yuyun Francis (@FrancisYuyun) reported 6 minutes ago

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

• 
  Harikrishna KP (@harikp2002) reported 7 minutes ago

  @AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!

• 
  Siddartha DevOps (@SiddarthaDevops) reported 7 minutes ago

  @AWSSupport link is not working

• 
  Jared Cassidy (@depach) reported 14 minutes ago

  @grhmc @QuinnyPig @awscloud Not fixed on mine I login every day 🥲 did you have to set anything?

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 15 minutes ago

  @AWSSupport I tried every possible combination to get phone support. I think it either just doesn't exist or it is down. Someone did get back to me in chat in another ticket tho.

• 
  Dhananjay (@DhananjayKhark2) reported 15 minutes ago

  @AWSSupport Case open since Aug 13 — 15 days, no fix! AWS Glue blocked with AccessDeniedException (account-level) in ap-south-1. NOT an IAM issue. Needs backend account verification sync. Case: 178661799100381 Please escalate! 🙏 #AWS #AWSGlue @awscloud @AWSCloudIndia

• 
  Kailash Tulsi Gajra (@kailashgajara) reported 17 minutes ago

  Is @awscloud down right now? #AWSDownAgain #AwsDown

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

• 
  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.

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

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

• 
  Priyanshu (@iproductAI) reported 27 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.

• 
  Brandon James (@brandonajames) reported 28 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  Base Builder (@basedbuilder_io) reported 36 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.

• 
  Onkar Deshpande (@i_am_onkar) reported 37 minutes ago

  @bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho

• 
  Arian van Putten (@ProgrammerDude) reported 38 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??)

• 
  jayesh somani (@Jayesh_Somani_) reported 39 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 🧵

• 
  Kartik Jain (@kartikjain0101) reported 40 minutes ago

  @awscloud you guy has lost your mind. payment got missing so team told me they will raising the request. account got hold, we have 250K unused credits, and now they are not initiation the account. wtf. our whole production is down.

• 
  barney (@Southclaws) reported 40 minutes ago

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

• 
  Dan Lynch (@danlynch) reported 41 minutes ago

  @QuinnyPig @awscloud I need to sign in with LEGO 😎

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

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

  @QuinnyPig @awscloud Not randomly redirecting to root console login page if I logged in with IAM identity center

• 
  zarrakh (@zarrakh) reported 43 minutes ago

  @AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws

• 
  niknak (@niknak) reported 48 minutes ago

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

• 
  Robat Das Orvi (@orvi_onethread) reported 50 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.

• 
  Ondřej Flídr (@snipercze) reported 54 minutes ago

  Hello @AWSSupport, is there any problem with EBS subsystem in us-east-2 (Ohio region)? Cannot resize volume (ending with internal error, same for console and CloudFormation), new volume is created but stuck in "Attaching" to the EC2. Thanks for check

• 
  Pixi Dust (@Bethco2257) reported 54 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.

• 
  Ranbir Mahapatra (@ranbirnxt) reported 1 hour ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  Kenton Parton (@kenton_parton) reported 1 hour 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?

• 
  Ümit Kaan Usta (@umitkaanusta) reported 1 hour 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

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