1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Amazon Web Services
  6. ❯
  7. 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 2
Pottstown, PA 1
Iztacalco, CDMX 1
Boca da Mata, AL 1
New York City, NY 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:

  • brandonajames
    Brandon James (@brandonajames) reported

    @callmeauntie218 Yes global outage from Amazon AWS.

  • xmubsx
    mubs (@xmubsx) reported

    @AWSSupport MFA team is in-house team or outsourced. This is not acceptable. It has been 3 months. In June '26 this issue started. If the MFA device or app is out of sync. How is it my problem. This is aws issue. How can you guys ignore a genuine issue like this. All articles are useless.

  • sir_divs_alot
    πŸ¦‹KieranπŸ¦‹ πŸ’» (@sir_divs_alot) reported

    @AWSSupport Thanks for your response and I've been keeping track for any updates very closely but the problem is these cases are either unassigned and if they are, no one is following up. I'm at the point of just giving up entirely cuz it's pointless waiting endlessly.

  • banhchugxanh
    banhchung (@banhchugxanh) reported

    @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

  • kakafa_btc
    kakafa.btc (@kakafa_btc) reported

    @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

  • VeraSimila
    Vera €⩊€ (@VeraSimila) reported

    @awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak

  • Jayesh_Somani_
    jayesh somani (@Jayesh_Somani_) reported

    It's Sunday 11:30 AM. Production is down. Users can't login. My phone won't stop buzzing. Every tool I tried to use to fix it β€” blocked. AWS had quietly quarantined our only admin IAM user. Here's how I restored production in 2 hours without AWS Support @awscloud 🧡

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

  • p_valuee
    Prateek Gupta (@p_valuee) reported

    @AWSSupport My entire production is down since 3 days, I believe this is a P1 and should be treated like one @AWSSupport. Please help me with an ETA

  • Ikenna_dev
    Ikenna Iheanaetu (@Ikenna_dev) reported

    @awscloud Runtime request flow User β†’ HTTPS β†’ ALB β†’ ECS Fargate β†’ Container The ALB handles HTTPS using ACM and routes traffic to the ECS service. The service runs multiple tasks across Availability Zones, giving the application redundancy instead of relying on one server.

  • krrawn
    krrawn (@krrawn) reported

    I was wondering why @awscloud support was slow the other day

  • chintan86
    Chintan Shah (@chintan86) reported

    @AWSSupport @awscloud Dues cleared, reinstatement requested β€” still waiting with no movement. My production workloads are down and every hour is costing us. Can someone please prioritise this? Case ID ready to share over DM.

  • jonny_castles
    Jonny Castles (@jonny_castles) reported

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

  • i_am_onkar
    Onkar Deshpande (@i_am_onkar) reported

    @bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho

  • silenthill_x
    masaki (@silenthill_x) reported

    @AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.

Check Current Status