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	7 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:

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

• 
  Alvaro Villalba (@alvarovillalbap) reported 8 minutes ago

  @philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?

• 
  M (@mdw864) reported 10 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

• 
  Jim Osman (@EdgeCGroup) reported 12 minutes ago

  @awscloud Real innovation starts with people solving real problems.

• 
  Maurizio Santamicone (@santamm) reported 14 minutes ago

  @awscloud And while you fix it, you can credit us for those amounts.

• 
  M (@mdw864) reported 15 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.

• 
  Silksteele (@silksteele) reported 15 minutes ago

  @adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.

• 
  GiveHateAChance (@HelpingHate) reported 16 minutes ago

  @awscloud It's cute how the ***** indians who caused all of this are never at fault and how you dismiss what a huge error this was with an emoji.

• 
  PositiveVibes (@KPTheFighter) reported 16 minutes ago

  @awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws

• 
  billy (@Billy17979063) reported 21 minutes ago

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

• 
  Keith Townsend (@CTOAdvisor) reported 22 minutes ago

  I spent over $120 in @awscloud so far this month. Most of it has been on GPU instances and Xeon 6. This is the most I've spent since I've had a long-running VM as a web app server a few years ago.

• 
  D (@D8118199174282) reported 24 minutes ago

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

• 
  Tseng (@TsengSR) reported 29 minutes ago

  @marcelocantos @awscloud I'm 100% certain you'd also crying a river when hard caps are added and the same happens again, because then your services will be shut down immediately until they resolve it and you'll cry too, how they'd dare to take your services offline when reaching the cap due to an error.

• 
  Maciej Wilczyński (@wilczynski24) reported 29 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.

• 
  Ignacio Cassinelli (@igncass) reported 32 minutes ago

  @awscloud What a terrible response

• 
  Donna Paulsen (@donnapaulparody) reported 32 minutes ago

  @VeryCoolGuy6 @awscloud Check the issues that happened in last 6 months and diagnosis/cause of the issue.

• 
  ErinE (@WhoaNowNelly) reported 35 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.

• 
  Jack Stone (@c0XhHxvylL) reported 35 minutes ago

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

• 
  mail box (@mailbox28564784) reported 37 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

• 
  AntDracula (@ant_dracula) reported 39 minutes ago

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

• 
  Jonny Castles (@jonny_castles) reported 40 minutes ago

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

• 
  matyas.dev (@DevMatyas28516) reported 45 minutes ago

  @AWSSupport Still nothing happened after a week, after I sent your X account our issues numbers.

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

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

• 
  Prof. D. Kumar (@DrDKumar_NRI) reported 49 minutes ago

  @AmazonHelp @amazonIN @awscloud Amazon pay UPI is blocked and can not verify device while other UPIs r working on porting the number. Been 03 days and the issue is still not resolved. LOOK INTO TICKET # V2289236874 and resolve at its earliest. Already cleared data, reboot!

• 
  Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported 49 minutes ago

  @awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!

• 
  The AI Therapist (@TheAIShrink) reported 50 minutes ago

  @MikeLongTerm @amazon @awscloud EC2 on AMD CPUs. The cloud bill goes down, the margins go up. aws is quietly fixing its cost structure while everyone watches the models. smart

• 
  Ironluca (@Ironlucaaa) reported 50 minutes ago

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

• 
  Priyanshu (@iproductAI) reported 54 minutes ago

  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.

• 
  Okko Ojala @okko@mastodon.social (@okko) reported 1 hour ago

  @edwarddonner @awscloud @AWSSupport Combine a bug like that and spending caps, and the services would have been taken down and caused major losses of services worldwide.