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

amazon-web-services-aws Hero Image

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

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
San Jose, CA 2
Los Angeles, CA 1
Greater Noida, UP 1
Hamburg, HH 1
Uniontown, PA 1
Birmingham, England 1
New York City, NY 1
Cali, Departamento del Valle del Cauca 1
Sandillon, Centre-Val de Loire 1
Charlotte, NC 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:

  • OLayer8 OSILayer8 (@OLayer8) reported

    @QuinnyPig @awscloud Move the cloud they say, it's resilient. It doesn't go down. Then it goes down. And they don't know how to fix it.

  • SIGSEGV23 SIGSEGV (@SIGSEGV23) reported

    @ashishlogmaster @QuinnyPig @awscloud It’s not a single region service. I had no problems with SSO at all during the incident. It worked like a charm in the EU regions.

  • Pelumiee Pelumi Malvin-Adejunmobi (@Pelumiee) reported

    BTW @awscloud was down over the weekend

  • skydodiya Aakash Dodiya (@skydodiya) reported

    Hey @awscloud, please fix SQS console search. It's very hard to search queue by name. Give it a try so you will understand.

  • CTOAdvisor Keith Townsend (@CTOAdvisor) reported

    Anyone out there actively talking to their @AWScloud account team about Outposts Server?

  • DanHugo Dan Hugo (雨果丹)(แดน) (@DanHugo) reported

    @AWSSupport While I appreciate the proaction, I was trying to be sarcastic, because, you know, the root problem enables all manner of priv elevation, so why not just have an installer do that, also, to apply the patch automatically by making use the vulnerability?

  • coates Sean Coates (@coates) reported

    Honest question: is there a security reason for not saying which bucket here, @awscloud team? “…NoSuchBucket: An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist” I can dig, but it sure would be helpful to see it inline.

  • gpapilion Geoffrey Papilion (@gpapilion) reported

    @QuinnyPig @awscloud Its really hard in large scale infra. Facebook’s badge system breaking is a good example during the routing outage. Auth, routing, and naming are often global things so when touching them, it requires lots of thought. Then since they are so foundational you can break everything

  • ZiggyTheHamster Keith Gable 🌻 (@ZiggyTheHamster) reported

    @simonggillett @QuinnyPig @awscloud I don’t think that they don’t know how to technical write, but rather that they’re not comfortable naming systems or architectural patterns, so it gets edited down to something that sounds less competent.

  • AaronBoothUK Aaron Booth (he/him) (@AaronBoothUK) reported

    @poiThePoi @QuinnyPig @awscloud Yeah not biased advice at all. Most people's risk profiles do not require multi region. The risk of having aws issues compared to the likelihood of breakages and issues due to your own poor implementation or losing skills in the workforce.

  • ryanseanbadger Ryan Badger (@ryanseanbadger) reported

    @jonnyplatt @awscloud 1. Email them and explain (I had a similar issue once and they refunded me) 2. Setup billing and monitoring alerts!

  • TonyOnTheTweetr Tony on the Tweetbox (@TonyOnTheTweetr) reported

    @QuinnyPig @awscloud In doing so most stuff recovered before we could even tell why it had broken. So here’s a partial description containing what little we do know for sure and a promise we’re going to theorize real hard about what we didn’t actually capture’

  • ashishlogmaster Ashish “Logmaster” (@ashishlogmaster) reported

    @QuinnyPig @awscloud Will be interesting how they will “improve” AWS SSO. We were SOL as we could not login at all! It’s a single region service and does not support “dual” instances (2 diff regions) by AWS org.

  • PietroStopponi Pietro Stopponi (@PietroStopponi) reported

    @AWSSupport B. Your staff made it clear from the start that this was your problem, your security breach. Nonetheless I had to spend a huge amount of time to secure the account, delete the resource ect. Why? who repays me all this time and stress? Why I was drag into this?

  • annaspies Anna Spysz 💉💉💉 (@annaspies) reported

    @mitabaxi @awscloud I'm kidding :) My #1 goal at AWS is to not cause a wide-scale outage that gets written about in the news

Map Check Current Status