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
Little Rock, AR 1
Atlanta, GA 1
Clearwater, FL 1
Monterrey, NLE 1
Rostock, Mecklenburg-Vorpommern 1
Oakville, ON 1
Glendale, AZ 1
Oakland, CA 1
Greater Noida, UP 1
Alamogordo, NM 1
San Francisco, CA 1
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
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:

  • PrometheusAIsec
    Trevor Skinner (@PrometheusAIsec) reported

    I’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.

  • TrbimixsQ
    Trbimixs (@TrbimixsQ) reported

    @AWSSupport i've finished, plz fix it soon

  • U_N_R_3_A_L
    Rahul Patel (@U_N_R_3_A_L) reported

    @AWSSupport I'm trying to reach out AWS support through chat but 1 hour in the chat and no one is joining, this is the 2nd time I'm facing this issue in month where I have to keep on waiting for the production issue.

  • winstonalien
    Winston (@winstonalien) reported

    Hey @AWSSupport @jeffbarr @Werner, case #177739024400953 has been open for 9 days now. AISPL account blocking ALL Bedrock access. AWS Founders Program member with $1,000 in credits I still cannot use. Every reply says "being investigated" with zero resolution. This is unacceptable. Can someone from Bedrock engineering actually fix this?

  • imTkorde
    Tejas Korde (@imTkorde) reported

    @AWSSupport hello AWS despite asking for multiple times to connect with the customer care executive I'm just getting we are working on it and I have to solve the issue today only please connect with the team it's highest priority task !

  • yiyine8
    いいね! (@yiyine8) reported

    @AWSSupport Urgent billing issue. My EC2 instances are still generating charges, but I cannot access my AWS accounts because the registered emails were deleted. Case ID: 177725454200231 Could someone please help review my case?

  • RyanRael16
    Woods (@RyanRael16) reported

    @Midnight_Captl The irony is genuinely remarkable. Every hyperscaler on earth confirms they cannot build infrastructure fast enough. Azure supply constrained at 40% growth. Meta raising capex to $145B. Amazon AWS growing 28% with no signs of slowdown. Google Cloud up 63%. All four saying they need more chips faster than anyone can deliver them. And Nvidia is down 4%. The only rational explanation is the market is pricing in custom silicon risk. If Microsoft, Meta, and Google are all building their own chips to supplement GPU supply the fear is Nvidia's pricing power erodes over time even as demand grows. That is a legitimate long term concern dressed up as a short term sell. But in the near term supply constrained hyperscalers raising capex is the single most bullish data point for Nvidia that exists. The market will figure that out. It usually does. Just not on the same day.

  • cb3_rob46858
    HRH Prince Sven Olaf of CyberBunker - CB3ROB (@cb3_rob46858) reported

    @awscloud then you end up with a leaking radiator, oil leaks and half the lights broken because noone ever can be ****** to change them on those horrid contraptions.

  • Ashish_Pawa_22
    Ashish Pawar (@Ashish_Pawa_22) reported

    @AWSSupport @AWSSupport Prioritized but still no call after 74 hours. Documents already sent. Need phone verification NOW. My business is down. Call +91-8275976388 immediately.

  • _cryptomofo
    cryptomofo (@_cryptomofo) reported

    @WatcherGuru Wouldn’t happen on $ICP.. No @awscloud NO PROBLEMS.. #CLOUD

  • HenriqueLi88059
    Henrique Lima (@HenriqueLi88059) reported

    @AWSSupport @awscloud Our medical imaging platform has been DOWN for 24+ hours. Real patients. Real exams. Real impact. AWS suspended with ZERO explanation and ZERO contact after opening. This is a Radiology/PACS system. Every hour matters. We are desperate for a response.

  • hailo_berto_9
    Hailo Berto, yê Elî (@hailo_berto_9) reported

    @AWSSupport I did add a new credit card, but I cannot do payment! this is the issue!! this is not very helpful!

  • Hershal0_0
    Hershal Rao (@Hershal0_0) reported

    @awscloud and here i am taking 3 business days to fix a single css bug

  • pelaseyed
    homanp (@pelaseyed) reported

    @0xMevu @specific_dev @awscloud It's a swarm of researches, we don't have issues with tool calls.

  • yiyine8
    いいね! (@yiyine8) reported

    @AWSSupport @AWSSupport Urgent billing issue. My EC2 instances are still generating charges, but I cannot access my AWS accounts because the registered emails were deleted. Case ID: 177725454200231 Could someone please help review my case?

Check Current Status