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
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:
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 |
|---|---|
| Pottstown, PA | 1 |
| Iztacalco, CDMX | 1 |
| Boca da Mata, AL | 1 |
| Township of Evan, KS | 1 |
| New York City, NY | 1 |
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:
-
Adel Bucetta (@adelbucetta) reported@tushaarmehtaa @OpenAIDevs @awscloud back to school is just a Band-Aid on a larger issue: how do we make building with ai accessible for the next 50 million people, not just 50?
-
ShenYubao (@ssybb1988) reported@AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932
-
jayesh somani (@Jayesh_Somani_) reportedIt'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 🧵
-
Samrat Singh (Sam) (@isamrats) reported@KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)
-
Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported@Cloudflare @awscloud Fix human verification
-
Rohit Dhawan (@rohitdhawan26) reported@AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.
-
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
-
Payal (@payal_codes) reportedDay 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.
-
Ranbir Mahapatra (@ranbirnxt) reported@QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?
-
BOB-DO-THEM (@osangesua) reportedThis is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies
-
Arian van Putten (@ProgrammerDude) reported@QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?
-
zarrakh (@zarrakh) reported@AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws
-
GIrls In Technology! (@francescaViking) reported@awscloud @amazonmturk are shuttering services barely months after announcing maintenance mode, giving barely a month now and leaving requesters and workers in the lurch. Amazon demonstrates again why it's terrible for businesses and users.
-
Somers (@jake__somers) reportedAWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport