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 (82%)
• Sign in (9%)
• Errors (9%)

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	2 days ago
New York City	Website Down	5 days ago
Ciudad Jardín	Website Down	30 days ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 months ago
Point Pleasant Beach	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:

• 
  Kish_lloyd (@kish_lloyd) reported 6 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 🤔

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

• 
  Indrani Som (@indrani_som2004) reported 21 minutes ago

  @Anjishnu46 @AWSSupport @AWSSupport look into this issue

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

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

• 
  Edward Donner (@edwarddonner) reported 25 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.

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

• 
  Matthew (@OneShotCaller) reported 28 minutes ago

  @CalebChamberla6 It’s an AWS billing error (see @awscloud)

• 
  Aramis Official (@AramisToken) reported 30 minutes ago

  @NoaSanderskyo7 @F1 @awscloud He was slow af, actually

• 
  Eszter Morvay (@eszter_morvay) reported 31 minutes ago

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

• 
  M (@mdw864) reported 32 minutes ago

  @awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged

• 
  J (@kankerhoerrrrrr) reported 33 minutes ago

  @marcelocantos @awscloud you're a moron. it was a known, and widespread issue, and they even had a notice in the health dashboard. this is a skill issue.

• 
  metis (@metis00001) reported 34 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

• 
  Anjishnu Ganguly (@Anjishnu46) reported 38 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.

• 
  Santhosh (@santhoshv) reported 42 minutes ago

  @D8118199174282 @AWSSupport Many stopped services, also I never assumed health issues with billing itself

• 
  Edward Donner (@edwarddonner) reported 43 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.

• 
  jd42 (@jdonovan42) reported 44 minutes ago

  @DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.

• 
  Ben Newton ベン (@BenENewton) reported 45 minutes ago

  @awscloud Somewhere there's an IT guy lying on the ground next to his desk after opening the page with this error on it.

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 46 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

• 
  Ing. Mario Varón M.Sc (@ma_varon_col) reported 47 minutes ago

  @AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...

• 
  Zyreon (@Zyreon_trading) reported 49 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..

• 
  AntDracula (@ant_dracula) reported 49 minutes ago

  @_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error

• 
  Gabe Fletcher (@gabefletcher) reported 51 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 ****.

• 
  Fikri Firdaus (@fikrfird) reported 51 minutes ago

  @awscloud This really isn’t something to joke about. A false billing alert at this scale can cause genuine panic and even serious health consequences. Some users may have rotated credentials, shut down workloads, or deleted services because they feared their accounts had been compromised.

• 
  Shobhit Shrivastava (@shri_shobhit) reported 52 minutes ago

  @adamr_1776 I left Amazon AWS around 2019. From what I recall it was something like issues dot Amazon dot com

• 
  Jack Stone (@c0XhHxvylL) reported 53 minutes ago

  @AWSSupport be honest, how much of this problem was due to ai and/or vibecoding

• 
  mail box (@mailbox28564784) reported 54 minutes ago

  @amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2

• 
  Mahadev Vyavahare (@mahadevkv) reported 54 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

• 
  Jonny Castles (@jonny_castles) reported 57 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

• 
  M (@mdw864) reported 59 minutes ago

  @AWSSupport Tells me to login when I keep telling you I cannot login because I don’t have the capability to do so.

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