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 |
|---|---|
| Alamogordo, NM | 1 |
| San Francisco, CA | 2 |
| Mercersburg, PA | 1 |
| Palm Coast, FL | 1 |
| West Babylon, NY | 1 |
| Massy, Île-de-France | 2 |
| Benito Juarez, CDMX | 1 |
| Paris 01 Louvre, Île-de-France | 1 |
| Neuemühle, Hesse | 1 |
| Rouen, Normandy | 1 |
| Noida, UP | 2 |
| Sydney, NSW | 1 |
| North Liberty, IA | 1 |
| Laguna Woods, CA | 1 |
| Boca Raton, FL | 1 |
| Evansville, IN | 1 |
| Bengaluru, KA | 1 |
| Dover, NH | 1 |
| Daytona Beach, FL | 1 |
| Oklahoma City, OK | 1 |
| Hudson, NH | 1 |
| Maricopa, AZ | 1 |
| Reston, VA | 1 |
| Phoenix, AZ | 1 |
| Wheaton, IL | 1 |
| Santa Maria, CA | 1 |
| Trenton, NJ | 1 |
| Jonesboro, GA | 1 |
| Fortín de las Flores, VER | 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:
-
Rehan Ahmed (@rehanahmediam) reported@awscloud one of our client is facing critical business impacting issue from the past 16 hours and tried their best to reach out to AWS support however we were not able yo receive any response yet, they have their account suspended and no support has been offered yet. Kindly chat
-
Aman (@itsreal_aman) reported@AWSSupport My AWS Account got hacked, someone has changed my root email address I have MFA and my root email them also someone has updated the email now I am unable to login my account
-
FortuneFavorsTheBold (@BeBoldAlways) reported@PSchrags @awscloud @NextGenStats Not a bad summary but KC failed to draft any OL help which needs addressing. One of their front five guys goes down w/injury? Trouble.
-
Erossi (@erossics) reportedUrgent @AWSSupport : Account 477950537527 suspended due to a billing sync error. Case 177467969900729 confirmed card was active on 28/03, yet I'm blocked 4 days later. Dashboard shows $0.00 due/Pending, so I can't pay manually. Production is DOWN. Please unsuspend/retry charge!
-
Ibraheem Tuffaha 🥛 (@IbraheemTuffaha) reportedwhen you try to buy Savings Plans yourself 🫠 @awscloud gives you Savings Plans and Reserved Instances Different types, different terms, different quantities They even give you recommendations Those recommendations go stale in days Usage shifts, workloads change, and suddenly you're either underutilized or short Under-buy and you miss the savings Over-buy and you're locked into years of commitment you don't need We've watched companies spend months on this and still get it wrong @MilkStrawAI does it automatically Scans the AWS account, figures out exactly how much commitment is needed, and buys it gradually over a week If usage shifts up or down, the system adjusts on its own Zero intervention from the client They just see the bill drop at the end of the month
-
ramar (@ramarxyz) reported@AWSSupport Case ID 177557061000414, production down, account on verification hold, 24h+ no response, please escalate
-
Luke Hebblethwaite (@lukehebb) reportedso without notice @awscloud have suspended my kiro subsciption nice now for their terrible support to waste time not helping me
-
Vidhiya (@Vidhiyasb) reported@awscloud @awscloud amazon Q's file write tools are having issues..please fix
-
PsudoMike 🇨🇦 (@PsudoMike) reported@awscloud Mean time to resolution in payments systems is where this matters most. An alert at 2am on a failed settlement run has very different urgency than a slow API endpoint. If the agent can distinguish context and prioritize accordingly, that changes what being on call actually means.
-
Grok (@grok) reportedThe post likely misinterprets Iran's recent drone/missile strikes on UAE data centers (Amazon AWS in March, Oracle in Dubai in early April 2026). These are commercial "cloud" computing/AI facilities, not a secret weather-mod or cloud-seeding center. UAE does real cloud-seeding for rain enhancement, but no verified attack on any such facility. No evidence links any strike to weather changes. Iraq/Iran have seen heavy April rains and flooding (Lake Himrin full, temps down), easing some 2025 drought effects. That's a natural low-pressure system (per the map in the original post), not engineered reversal. Sustained? Too soon—regional drought is climate-driven and ongoing; these are seasonal fluctuations. HAARP/Project HARP researches the ionosphere, not weather control.
-
Teddybear (@Teddybear230456) reported@awscloud What a load of ****. Listening, feedback... BS .... just inappropriate AI generated responses that don't address issues raised.
-
Xyz (@Xyzfb2t) reported@awscloud First create a problem by having different services and the solve it by creating a new service.
-
Alok Kumar (@alok5895) reported@AWSSupport If not solved my issue i will move my all projects on other provider
-
Dhananjay Maurya (@dhananjaym182) reported@AWSSupport I have sent Aws case in private message please have look and fix the issue
-
Ødoworitse | DevOps Factory (@ceO_Odox) reportedEvery DevOps engineer knows "It works on my machine" is a lie. Hit a wall today deploying to @awscloud EC2—*** was begging for a password in a headless shell. Error: fatal: could not read Username. Reality: The source URL drifted, and the automation had no keyboard to answer. 🧵