Amazon Web Services 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:

• 
  kyun anon (Gobhi ka fool ) (@anondis1122) reported 6 minutes ago

  @AWSSupport @ashu_sharma17 Yeah. Why tf not send an email.. that there is an issue. I have a medical condition. It put my life in danger

• 
  GiveHateAChance (@HelpingHate) reported 7 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.

• 
  Mon (@mon73x) reported 11 minutes ago

  @asimrazax @AWSSupport I have the same problem. Did you fix it?

• 
  Shaaaaaaaaan (@AryavartKSamrat) reported 15 minutes ago

  @Sahilvyas29 @JeffBezos @AWSSupport Its a amazon glitch man. Read about it.

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

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

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

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

• 
  M (@mdw864) reported 18 minutes ago

  @AWSSupport Five months of broken links & blocked support channels is unacceptable. You have more cut off core business services because you have refused to provide a person with disabilities a way to tell you that you are over billing me. Escalate to a senior rep to fix this before 9am cst

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

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

• 
  That Other Hecate (@HecateKeys) reported 25 minutes ago

  @OwenGregorian 1) Forgets how DNS works. AWS goes down for days. 2) Forgets how arithmetic & metering works. Trillion-dollar bills for scant usage. @awscloud Regretting all those mass layoffs of your veteran engineers yet?

• 
  sof ࿔˚⋆ (@sophia_ray_17) reported 29 minutes ago

  @awscloud until the cloud has a power outage and i can't get into my car

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

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

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