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%)
• Errors (22%)
• Sign in (11%)

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	4 hours ago
Township of Evan	Website Down	15 days ago
New York City	Website Down	17 days ago
Ciudad Jardín	Website Down	1 month 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:

• 
  Ivan Toma (@FounderRAVERK) reported 4 minutes ago

  @awscloud @Google @Microsoft The water problem is only going to get bigger. We already have technology that can help data centers produce their own cooling water from the sea. Let’s solve this together.

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

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 6 minutes ago

  @AWSSupport Again there is a mass wave of suspensions like in May I'm assuming in error as I've been on this platform for over 10 years and this seems to be happen more frequently. Emails from mturk-noreply havent worked in a long time,any updates on this situation @amazonmturk

• 
  ShenYubao (@ssybb1988) reported 6 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

• 
  ✨Neil Blumenthal (@MrKryptonBTC) reported 6 minutes ago

  @AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time

• 
  Edward Donner (@edwarddonner) reported 7 minutes ago

  @darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.

• 
  Edward Donner (@edwarddonner) reported 7 minutes ago

  @BaconOverflow @awscloud I'm an experienced technologist. Yes a bug was likely. My fear was I'd made a terrible mistake or leaked credentials. AWS customers are on the hook for either. AWS has no hard caps. My initial alerts were high but not billions. For 10 mins I thought this just might be real.

• 
  The Trading Guy (@thetradingguy_) reported 8 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?

• 
  Jim Osman (@EdgeCGroup) reported 9 minutes ago

  @awscloud Real innovation starts with people solving real problems.

• 
  TeeBeeCTO (@TeeBeeCTO) reported 10 minutes ago

  Setting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!

• 
  Gabe Fletcher (@gabefletcher) reported 11 minutes ago

  @marcelocantos @awscloud bro... touch some ******* grass. OF COURSE IT WAS AN ERROR. WHO REALLY THINKS THEY LOOK AT THEIR AWS BILL FOR A TRILLION DOLLARS AND SAYS "OH THATS DEFINITELY REAL" stop. go **** off to some VPS's or some ****.

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 18 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

• 
  Mario Giampieri (@mario_giampieri) reported 19 minutes ago

  @AWSSupport Another update- I received a canned response explaining to me what sign in credentials are and sending me a link to open a new account. Eleven months of this.

• 
  Anjishnu Ganguly (@Anjishnu46) reported 19 minutes ago

  I posted again that day because the same issue was blocking our AWS Activate application too. @AWSSupport said it had been passed along again. Another public reply, same unusable account.

• 
  🔥 PHOENIXX🔥 (@AIPulse0) reported 28 minutes ago

  AMAZON AWS PAYS $127K/MO FOR CLOUD COMPUTING. SERGEY BOUGHT CHEAP SERVER RACK + CLAUDE AI. MAKES $318K Pause at 0:11 — rack with 40+ servers. Every indicator glows green. This is local computing. Zero latency. Zero cloud bills. Sergey, 35, Ukraine. Was AWS architect, $7,200/month. Understands: companies pay Amazon millions, but they can do same calculations locally. Bought used server rack for $4,800. Installed Claude AI for local processing. 78 companies pay $4,077/month each instead of $12K on AWS. Amazon offered $4,200,000. Sergey said: "You profit from dependency. I profit from freedom." Why — in video.

• 
  Ritesh Roushan (@devXritesh) reported 33 minutes ago

  A good architecture starts by separating document storage, signing, identity verification, and notifications into independent services. 1. API Gateway All requests (upload, sign, download, share) pass through the API Gateway. It handles authentication, rate limiting, request validation, and routing. 2. Document Service Contracts are uploaded directly to object storage (Amazon S3/GCS/Azure Blob). Metadata such as owner, participants, document status, and version history is stored in PostgreSQL. Large files never pass through application servers. 3. Identity Verification Service Before signing, users verify their identity using email OTP, SMS OTP, OAuth, or KYC providers depending on compliance requirements. A verified identity token is issued before allowing signatures. 4. Signing Service Each signature request creates an immutable signing event. Documents are locked while applying a signature to prevent conflicts when multiple users sign simultaneously. Optimistic locking or version numbers help resolve concurrent updates. 5. Audit Log Service Every action upload, view, download, sign, reject, revoke is published to Kafka. Events are stored in an append-only audit database with timestamps, signer identity, IP address, and device information, creating a tamper-resistant audit trail. 6. Notification Service Kafka events trigger email, SMS, and push notifications asynchronously so users are notified instantly without slowing down API responses. 7. Security • Encrypt files at rest (AES-256) • TLS for data in transit • Short-lived signed URLs for downloads • RBAC for document access • Hash every signed document (SHA-256) to detect tampering • Store digital certificates securely using a KMS/HSM 8. Scalability Deploy services independently behind load balancers. Use Redis for caching document metadata and sessions. Object storage handles millions of documents, while Kafka decouples services and absorbs traffic spikes. Read replicas improve download performance, and multi-region replication ensures disaster recovery. This architecture provides secure storage, concurrent signing, legal compliance, high availability, and scales to millions of contracts worldwide.

• 
  JoeFromSJersey (@JoeFromSJersey) reported 39 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.

• 
  metis (@metis00001) reported 40 minutes ago

  @AWSSupport Looks like it has been resolved. But it definitely took like 5 days to resolve a payment configuration issue! Thanks for reaching out.

• 
  Keith (@happy_keith) reported 42 minutes ago

  @amazon @awscloud @AmazonUK What does it take to get you to respond to a serious problem DO NOT tell me to go to customers services AI as it is incapable of responding to the issue This is a complete farce !!!!!!

• 
  kakafa.btc (@kakafa_btc) reported 48 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

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

• 
  ErinE (@WhoaNowNelly) reported 50 minutes ago

  @DRiceHockey @WNBA @awscloud Same applies to all their stats. Their PRA is gonna go down too. That's the nature of injuries. Makes it harder for the individual, but does not increase the difficulty of the actual shot itself.

• 
  Mohammed Nafees (@mnafees) reported 51 minutes ago

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

• 
  JJ Ferman (@jjferman) reported 51 minutes ago

  @awscloud the fix: if bill > 1 quadrillion: we have a problem...

• 
  SwarmOne.ai (@swarmoneai) reported 52 minutes ago

  OpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud

• 
  D (@D8118199174282) reported 59 minutes ago

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

• 
  Brandon James (@brandonajames) reported 60 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  devastatindave.eth (@NftCelestials) reported 60 minutes ago

  @awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually

• 
  Luke Skywalker (@LSF4Life1981) reported 1 hour ago

  @RinoTheBouncer Just like you can't be bothered to Google anything PSN issue was @awscloud which doesn't say anything either

• 
  BOB-DO-THEM (@osangesua) reported 1 hour 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