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 (67%)
• Sign in (17%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Boca da Mata	Errors	8 days ago
Township of Evan	Website Down	22 days ago
New York City	Website Down	25 days ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	3 months ago
Chennai	Website Down	3 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:

• 
  Eszter Morvay (@eszter_morvay) reported 2 minutes ago

  @AWSSupport Also - apologies for the DM issues, i just changed my settings, so DMs should work now

• 
  Ondřej Flídr (@snipercze) reported 3 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

• 
  Ikenna Iheanaetu (@Ikenna_dev) reported 4 minutes ago

  @awscloud Runtime request flow User → HTTPS → ALB → ECS Fargate → Container The ALB handles HTTPS using ACM and routes traffic to the ECS service. The service runs multiple tasks across Availability Zones, giving the application redundancy instead of relying on one server.

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

• 
  D (@D8118199174282) reported 8 minutes ago

  @awscloud No, you still haven’t compensated users for the cost bug error

• 
  Corey Quinn (@QuinnyPig) reported 14 minutes ago

  Kinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.

• 
  M (@mdw864) reported 19 minutes ago

  @AWSSupport Either that or ask me to login, which I keep telling you I cannot login. It has nothing to do with 2FA. That is not the issue.

• 
  Corey Quinn (@QuinnyPig) reported 23 minutes ago

  I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

• 
  Har (@duckboy1909) reported 23 minutes ago

  @awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon

• 
  John Darin Holloway (@bofkentucky) reported 26 minutes ago

  @QuinnyPig @awscloud Hopefully better than the "new" broken elastic beanstalk console experience.

• 
  Open_ERV (@open_erv) reported 27 minutes ago

  Unfortunately although they appear to be awesome people BrambleCFD is turning out to not be that hot. The main problem is the relationships/what they do of all the different settings is ridiculously opaque. There is no documentation. Their solution is to try to explain things in a video call, and if you need help, you ask for it, which it takes a week or more to get any kind of answer from an actual human, not because they are doing anything wrong but that's just not a good system. It's a long long way from the useability of simscale. I did however uncover an option that might be reasonably good, which is a virtual machine that I pay for the core-hours on. In many ways this is better. I can work directly with openFOAM and one of the front ends on a high powered linux computer with hundreds of gigs of ram and 96 high powered cores, and still only pay for what I use, theoretically. The openFOAM foundation has a system worked out ad directly offers the service, unfortunately they in turn use the amazon AWS or the microsoft Azure system, but what can you do. There are other companies that do similar things, but they probably aren't as well done as the one from the actual foundation. I think I'll try that one first. Having an AI in a harness on the machine is probably going to be indispensable, but I'll be using it primarily as a learning tool rather than asking it to do everything for me. I have been able to set up CowAgent, which is kind of basic but seems to work ok, with DeepSeek. A "harness" allows the AI to run commands on your computer and read the output automatically, as well as the other things web chat stuff can do. Secondly, it can store information in files and run the AI in a loop, doing many inferences one after the other, thus getting far more done than a web chat can (actually they might do something similar now IDK but they don't seem to).

• 
  Siya (@reze_xqc) reported 29 minutes ago

  @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

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

• 
  Samrat Singh (Sam) (@isamrats) reported 32 minutes ago

  @KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet

• 
  Dhanush N (@Dhanush_Nehru) reported 39 minutes ago

  Opened a support portal ticket on AWS. For a week, I heard nothing. contacted @AWSSupport by direct message and the issue was resolved in a matter of days. Their team still responds to thousands of queries every day. That's how genuine support appears. Thank you AWS!

• 
  absk (@abskwdkr) reported 40 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  𝙵𝚊𝚒𝚣𝚎𝚕 𝙿𝚊𝚝𝚎𝚕 ⚡️ (@FaizelPatel143) reported 41 minutes ago

  “AI will solve real problems, for the continent.” #AWSSummit2026 @awscloud

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

• 
  Kartik Jain (@kartikjain0101) reported 45 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.

• 
  Chintan Shah (@chintan86) reported 46 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.

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

• 
  Mohammed Nafees (@mnafees) reported 50 minutes ago

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

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

• 
  Harikrishna KP (@harikp2002) reported 53 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!

• 
  ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported 53 minutes ago

  @ishanxtwt Simply DNS server problem never take down an entire website. Except, like amazon AWS, are using domain and dynamic name resolve to working correctly between multiple servers and services.

• 
  Eemanuel (@Chukwunons63680) reported 54 minutes ago

  @nvidia @awscloud @grok what is the CPU server for?

• 
  BOB-DO-THEM (@osangesua) reported 56 minutes ago

  This is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies

• 
  JoeFromSJersey (@JoeFromSJersey) reported 57 minutes ago

  @AWSSupport Good morning folks, I appreciate the help getting things working for me yesterday as I was able to use Kiro! I'm not unable to upgrade from free tier though and get an error that says unable to upgrade. I've a case for that too and was hoping you could also get eyes on that.

• 
  Harun R. (@harundotdev) reported 59 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.

• 
  Quoc Huy (@q_huy_ngo) reported 1 hour ago

  @Cloudflare @awscloud mine transacted with Cloudflare about 700M times because of a broken DO alarm 🥲 no users, just a dev app, then a $655.83 bill. i fixed it and opened case 02252354 a month ago. still no billing decision and now i’m downgraded. can someone pls help? i really can’t afford this