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
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
Laguna Woods, CA 1
Boca Raton, FL 1
Evansville, IN 1
Bengaluru, KA 1
Dover, NH 1
Daytona Beach, FL 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:

  • tsonubin
    tsonubin (@tsonubin) reported

    Anybody experiencing login issue with AWS CLI? @awscloud @awssupport

  • walls_jason1
    Jason Walls (@walls_jason1) reported

    No cursor or AWS, but I have a AWS credits. @awscloud and honestly it was probably user error but @cursor_ai I seemed to demolish me credits? Is this the “stack”people are using?

  • basimkhalid
    Basim Khalid (@basimkhalid) reported

    @nygma504 @AWSSupport @awscloud Its down for me too. Any ETA please?

  • MshenguMasia
    XXX (@MshenguMasia) reported

    @Mikedotcoza His offer is insulting to the RSA community. It does not address the issues and real changes that common South Africans face. Others invest, such as the Amazon AWS project and Microsoft. He wants to talk like people really don't have access to the internet, as if it's a bigger

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

  • Stunner_99
    zI£|~ (@Stunner_99) reported

    @AWSSupport Yes I have. But on socials all other direct platform is not working

  • winstonalien
    Winston (@winstonalien) reported

    Hey @AWSSupport, case #177739024400953 open for 2 days, AISPL account blocking all Bedrock access, Founders Program member. Daniel escalated but still no fix. Can someone help?

  • BajaDavidlak
    Dave L 💜🛡️ (@BajaDavidlak) reported

    @Harryhwrqx @chainlink @awscloud and price goes down

  • jlgolson
    Jordan Golson (@jlgolson) reported

    @AWSSupport This is ******* ridiculous at this point. After a half dozen back and forth emails, the guy finally says "Also, after reviewing this request, I noticed a few things were not addressed and would like to clarify these. First, I see you mentioned that you're having trouble with an AWS Builder ID and not the account management console. Please note that an AWS Builder ID complements an AWS account, but it is separate from the AWS account and its sign in credentials." NO KIDDING, THAT IS WHY I SPECIFICALLY SAID IT WAS AN AWS BUILDER ID AND WAS SEPARATE FROM MY AWS ACCOUNT AND I COULD LOG INTO MY AWS CONSOLE JUST FINE. Explain to me what to do, because it seems like you are failing to THINK BIG and that you have zero BIAS FOR ACTION, so INVENT AND SIMPLIFY so that you can EARN TRUST and if you DIVE DEEP and do better, I'll DISAGREE AND COMMIT, got it?

  • ceO_Odox
    Ødoworitse | DevOps Factory (@ceO_Odox) reported

    Every 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. 🧵

  • alurmanc
    Alan Urmancheev (@alurmanc) reported

    @version_7_0 @awscloud Explain your point, what's the problem?

  • introsp3ctor
    Mike Dupont (@introsp3ctor) reported

    @AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems

  • alok5895
    Alok Kumar (@alok5895) reported

    @AWSSupport If not solved my issue i will move my all projects on other provider

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

  • igrgavilan
    Ignacio G.R. Gavilán (@igrgavilan) reported

    @awscloud_es @AWS @awscloud I need to talk urgently with you. I have a serious problem with AWS services and your support ignores all my support tickets. I prefer an in-person contact, in spanish if possible.

Check Current Status