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
Township of Evan, KS 1
New York City, NY 1
Ciudad Jardín, MEX 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:

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

  • QuinnyPig
    Corey Quinn (@QuinnyPig) reported

    I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

  • D8118199174282
    D (@D8118199174282) reported

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

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

  • drabs_i
    IDrabs (@drabs_i) reported

    @PlayStation @awscloud Wtf you playing at fix the outage.

  • GettingMyGlitch
    GettingMyGlitchOff (@GettingMyGlitch) reported

    @AWSSupport Yeah its just getting automated responses to everyone saying "Your account will not be re-opened. We regret that we have not been able to address your concerns to your satisfaction." so can you send the mturk team a message to review the error since its more then just me its

  • duckboy1909
    Har (@duckboy1909) reported

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

  • ashmit105
    Ashmit Dutta (@ashmit105) reported

    @awscloud keeps charging me $60 a month. I can’t login to my account due to a deprecated email. Making support tickets goes nowhere. Anyone got advice on what to do?

  • CastleEL88
    Meo Meo (@CastleEL88) reported

    @awscloud Focus on AI features instead of server maintenance. .

  • thewebbie
    Matthew Feinberg (@thewebbie) reported

    @infoscav @awscloud 28 Billion! AWS has acknowledged there is a problem with the billing console.

  • GamerUPGaming
    GamerUP (@GamerUPGaming) reported

    @TheRavenHelm man... are you detective seeds right? this is a new profile name ? whatever.. the "digital only direction" was announced more than 3 weeks ago.. not last week.. PSN servers are hosted by Amazon AWS, and amazon AWS had some disruptions today, they already solved the issue.

  • payal_codes
    Payal (@payal_codes) reported

    Day 1 : "How to Scale an App to 10 Million Users on AWS" If I have to design a system for 10 million users, I won't build everything on Day 1 because it will add unnecessary complexity and cost. I'll start simple with one application server and one database. As traffic grows, if the server starts reaching its CPU, memory, or storage limits, I'll first scale vertically by moving to a bigger instance. Once that is not enough, I'll separate the backend and database so both can scale independently. To avoid a single point of failure, I'll deploy the application across multiple Availability Zones and put a Load Balancer in front so if one server or AZ goes down, traffic is automatically routed to healthy servers. As the number of users keeps increasing, I'll make my application stateless by storing sessions in Redis. This allows me to add multiple application servers behind the Load Balancer and scale horizontally. If my database starts getting overloaded with reads, I'll use Redis to cache frequently accessed data and add read replicas to distribute read traffic. For static assets like images, CSS, and JavaScript, I'll store them in Amazon S3 and serve them through CloudFront so requests don't keep hitting my application servers. If traffic suddenly spikes during sales or events, I'll enable Auto Scaling with CloudWatch metrics so AWS automatically adds or removes servers based on demand. As the application becomes larger, I'll split the monolith into microservices. This allows each service, like authentication, payments, or notifications, to scale independently instead of scaling the entire application. If the database becomes the bottleneck, especially for write operations, I'll use sharding or federation depending on the data and business requirements. Finally, when users are spread across the world, I'll deploy the application in multiple AWS Regions to reduce latency and improve availability. My approach is always the same: find the bottleneck, solve that bottleneck, and only introduce more complexity when the current architecture can no longer handle the traffic.

  • _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. @AWSSupport

  • doktorgphd
    Gabriel (@doktorgphd) reported

    @awscloud wow really??? i had to search x for the reason?? not even an email?? I saw the email sent yesterday about the cost alert and I spend the last hour trying to work out what is going on because it looks very legit and I only find out it was an error on x! Just had to send an email!!

  • Param_eth
    Param (@Param_eth) reported

    The downfall of Storj Labs (bankruptcy): - launches Storj in 2014 to build a decentralised alternative to cloud storage - promises a blockchain based competitor to Amazon S3. - attracts thousands of node operators across the world - raises around $35 million in funding - secures roughly $30 million through its 2017 token sale - spends years building its decentralised storage network - the DePIN business model proves difficult to scale profitably 2021: - $STORJ reaches its all time high 2022–2025: - the token enters a prolonged decline - node operators report declining rewards and operational issues - Storj begins selling non-core assets and right sizing operations October 2025: - Inveniam Capital Partners acquires Storj Labs - the acquisition is expected to strengthen the company's future - financial pressures remain unresolved July 2026: - Storj Labs files for Chapter 11 bankruptcy protection - the company says legacy liabilities can no longer be outgrown - assets and liabilities are estimated between $1 million and $10 million > operations > customer services > the storage network continue running - Inveniam backs the restructuring process - Storj proposes a plan that could give STORJ token holders equity in the reorganised company - $STORJ falls another 14–15% after the bankruptcy announcement - the token is down roughly 99% from its 2021 all time high

Check Current Status