1. Home
  2. Companies
  3. Amazon Web Services
  4. Outage Map
Amazon Web Services

Amazon Web Services Outage Map

The map below depicts the most recent cities worldwide where Amazon Web Services users have reported problems and outages. If you are having an issue with Amazon Web Services, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Amazon Web Services users affected:

Less
More
Check Current Status

Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Ciudad Jardín, MEX 1
Kyiv, Kyiv City 1
Chennai, TN 1
Check Current Status

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:

  • D8118199174282
    D (@D8118199174282) reported

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

  • NotUnHackable
    Aaryan Bansal (@NotUnHackable) reported

    @awscloud that issue was happening since yesterday dude. why tf did it take so much time?

  • ant_dracula
    AntDracula (@ant_dracula) reported

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

  • OneShotCaller
    Matthew (@OneShotCaller) reported

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

  • ArashSadrieh
    Arash Sadrieh (@ArashSadrieh) reported

    @AWSSupport Hi @mattsgarman our whole service is down for almost 3 hours, would appreciate some help here ,eta on fix would be great

  • Mr_Honkitude
    Mr. Honkitude (@Mr_Honkitude) reported

    @St0ner1995 @AWSSupport When you owe someone $10k, you have a serious problem. When you owe someone $110 billion, they are the one with a serious problem.

  • dvtoever
    Daniël (@dvtoever) reported

    @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

  • duckboy1909
    Har (@duckboy1909) reported

    @awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon

  • _adam_here_
    Adam Peterson (@_adam_here_) reported

    @AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.

  • edwarddonner
    Edward Donner (@edwarddonner) reported

    @okko @awscloud @AWSSupport That's why it's opt in. Netflix would likely not opt in and be fine with the risk. You could join them if you wish. I would prefer to face an outage if AWS has another billing disaster than have unbounded exposure.

  • devXritesh
    Ritesh Roushan (@devXritesh) reported

    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.

  • JaoyadCode
    Md Jaoyad (@JaoyadCode) reported

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

  • abhibavishi
    Abhi Bavishi (@abhibavishi) reported

    Seems like a major glitch with @awscloud

  • ant_dracula
    AntDracula (@ant_dracula) reported

    @kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.

  • _virusbug_
    Ashutosh Dubey (@_virusbug_) reported

    @AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue.

Check Current Status