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 (80%)
• Sign in (10%)
• Errors (10%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Website Down	6 days ago
New York City	Website Down	9 days ago
Ciudad Jardín	Website Down	1 month ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 months ago
Point Pleasant Beach	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:

• 
  Zyreon (@Zyreon_trading) reported 2 minutes ago

  @awscloud When i wake up i saw:there is another AWS Bug/Service Down. Lol cannot give up time of 24 hours/7 days/infinity uptime..

• 
  Nilesh (@nile3h) reported 3 minutes ago

  Reached out to @awscloud team yesterday related to billing issues wrt AWS partners, no replies Can anyone help?

• 
  Daniël (@dvtoever) reported 7 minutes ago

  @marcelocantos @awscloud Totally agree. I my took hours for the stress to leave my body. I tought i was hacked and my services were abused. They didnt bother to take down the billing page temporarily with a warning or sent a follow up mail pointing out this bug.I am going to close down my account as well

• 
  Ironluca (@Ironlucaaa) reported 8 minutes ago

  Heyo again @AWSSupport, thanks for fixing the issue! My bill is only $503 now. That's much better, it's okay now!

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

• 
  Adam Peterson (@_adam_here_) reported 16 minutes ago

  is @AWSSupport down?

• 
  Jim Osman (@EdgeCGroup) reported 16 minutes ago

  @awscloud Real innovation starts with people solving real problems.

• 
  Certified AI Dev (@MisterPrashant) reported 16 minutes ago

  This solution to this problem is AI traffic monetization. If you are an owner of a platform that provides some valuable data, you can put the data behind a paywall for the AI traffic by charging the bot fraction of a penny for using your content. x402 Payment Required protocol tells the bot that the content requires payment and the bot settles the transaction quickly on a stable coin at which point the content becomes accessible. This way,people running their search bots does not require subscription to 10 different services and can easily access data from anywhere at a very minimal cost and the owners of the sites also win as the traffic count to their paywalled site will generate income. This is not a concept. The framework to build this is already available in @awscloud today.

• 
  D (@D8118199174282) reported 17 minutes ago

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

• 
  metis (@metis00001) reported 18 minutes ago

  I can't understand why AWS has not been able to resolve my issue of payment method. Whatever credit card I put, they are not able to verify it and they keep asking me to call the card issuer. It's not card issuer issue! @awscloud

• 
  J Bret Edwards (@jbecompslns) reported 19 minutes ago

  did @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.

• 
  Koray Yersel (@korayyersel) reported 20 minutes ago

  @AWSSupport My balance went down to zero. Time to delete the aws account

• 
  billy (@Billy17979063) reported 26 minutes ago

  @fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too

• 
  (au)stin (@stin_reece) reported 26 minutes ago

  @awscloud $50,000,000,000 says this was a vibe code error

• 
  V0LYX (@0xV0LYX) reported 28 minutes ago

  @awscloud clear communication like this builds trust fast the fix matters but the transparency matters more

• 
  Jan Jezek (@jbodl) reported 29 minutes ago

  @awscloud First you sent alerts that the account was over budget by 6-figure numbers. When the user logged in, the billing console confirmed the same. No banner there was an issue, no followup email, nothing. Just wannabe funny jokes on X. Seriously, AWS?

• 
  lak-alak (@baricadelane) reported 31 minutes ago

  @IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?

• 
  Brandon James (@brandonajames) reported 34 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  Kish_lloyd (@kish_lloyd) reported 39 minutes ago

  @AWSSupport Why does this feel like a stage for subscriptions hikes on other hosting providers. Previously human error was deemed the highest risk for error but if humans made AI 🤔

• 
  Md Jaoyad (@JaoyadCode) reported 39 minutes ago

  @awscloud you should fix it otherwise people will become sick after watching the bill!

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 41 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

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

• 
  D (@D8118199174282) reported 45 minutes ago

  @AWSSupport Will the affected accounts be compensated for this issue?

• 
  Maciej Wilczyński (@wilczynski24) reported 46 minutes ago

  @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

• 
  Mahadev Vyavahare (@mahadevkv) reported 49 minutes ago

  @SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud

• 
  Master of Controversy (@THe0GAmer) reported 54 minutes ago

  @Pirat_Nation Amazon aws outage knocked psn offline for 8 hours while sony pushes an all digital future fans could not launch their purchased games

• 
  Anjishnu Ganguly (@Anjishnu46) reported 56 minutes ago

  Hey @AWSSupport, Our Case 178452910500907 is still not resolved, and we've been left waiting without any meaningful update. Because of this, we're also unable to apply for AWS Activate, which is directly impacting our business operations and slowing down our workflow. This delay is becoming unacceptable. Please look into this urgently and help resolve it as soon as possible.

• 
  Christian Nonis (@christiannonis) reported 57 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  mail box (@mailbox28564784) reported 57 minutes ago

  @amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l

• 
  Ritesh Roushan (@devXritesh) reported 1 hour 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.