Amazon Web Services down? Current status and problems

Problems in the last 24 hours

The graph below depicts the number of Amazon Web Services reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Errors (38%)
• Website Down (35%)
• Sign in (27%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Paris 01 Louvre	Website Down	3 days ago
Neuemühle	Errors	3 days ago
Rouen	Website Down	3 days ago
Noida	Errors	4 days ago
Noida	Sign in	6 days ago
Sydney	Sign in	9 days ago

Full Outage Map

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:

• 
  Benjamin Smedberg (@nsIAnswers) reported 4 minutes ago

  The @awscloud SDK for JavaScript v3 is... really bad. Poor developer ergonomics. Really terrible docs. Missing config so that it doesn’t work in kubernetes!? Recommendation: stick with v2.

• 
  John Kelvie (@jpkbst) reported 6 minutes ago

  @aronchick @QuinnyPig @awscloud I mean, that's funny, but being sarcastic and caustic is exactly what people do not want that are having a vendor-inflicted outage. I think you are perfectly modeling the stereotyping I'm referring to.

• 
  SimpleTix (@SimpleTix) reported 12 minutes ago

  . Microsoft @Azure had a global outage this evening. This affected our platform for about 40 minutes. All event pages are up now. Please plan to move to @awscloud next week to increase our uptime. #Azuredown

• 
  Youri Ackx 🚲🐍🍗 (@YouriAckx) reported 14 minutes ago

  @awscloud #AWS now issues invoices with 1. company name (not *my* name) 2. company VAT number 3. Invoice date (not the print date or the invoice period) ✨👏 I know, we in Europe make things complicated.

• 
  𝕿𝖗𝖎𝖟 (@ItsJustTriz_) reported 16 minutes ago

  @AWSSupport Im actually getting a `Socket hang up` error due to a network failure on your end... Is this something you can look into?

• 
  кг|sтоf вегиаегт (@ssstofff) reported 19 minutes ago

  @AWSSupport none of the problems listed. i have this from time to time. i have this for ex with a new server i migrated from linode with exact same setup. that ran 1,5y without any interruption. on the health dashboard i see nothing.

• 
  John Kelvie (@jpkbst) reported 20 minutes ago

  @aronchick @QuinnyPig @awscloud You only need an account shut down for an hour or two for arbitrary reasons, with no obvious recourse, before you say "never again"

• 
  ShotByGL514 (@shotbygl514) reported 22 minutes ago

  @Outriders maybe if the servers were on @awscloud down time wouldn't happen ;)

• 
  Corey Quinn (@QuinnyPig) reported 26 minutes ago

  @aronchick @jpkbst @awscloud I’m talking in the “my account has been limited / deactivated and my business is currently down” sense.

• 
  tidyup (@tidyupmyworld) reported 27 minutes ago

  @AWSSupport Thanks...they have resolved my issue promptly...absolutely good service ..love you guys...cheers

• 
  Sabarfun ⚧️ 🏳️‍⚧️ (@sabarfun) reported 30 minutes ago

  I canceled my @Amazon #Prime and had already stopped ordering most products (and won't develop for @awscloud ) from them due to continuous issues with shady sellers. This thing where they're going to use AI to monitor drivers is just wrong. $AMZN

• 
  Feross (@feross) reported 35 minutes ago

  @rushiv @steely_glint @ibc_tw I mean, you can do this from any site that lets you type text in a box or upload files. GitHub Pages, Amazon S3, Google Docs, Dropbox, or a regular old web server can be used for spear-phishing. When they're targeting a single user, they're not likely to be caught.

• 
  Corey Quinn (@QuinnyPig) reported 41 minutes ago

  Note that many @awscloud blog posts and tutorials make this assumption about IAM roles, otherwise every post would be 2/3 IAM policy creation by volume. This is a separate problem.

• 
  Michael Migdol (@mmigdol) reported 41 minutes ago

  Anyone else experiencing problems with @proofpoint blocking certain IP addresses from @awscloud's SES servers? Problem started a couple of days ago.

• 
  Jen Hong (@the_jenhong) reported 42 minutes ago

  @AWSSupport Seriously. You're supposed to respond within 1 hour yet we haven't been able to reach anyone in 12 hours. Please, respond and help fix the issue created by your system failure. I've never experienced this level of poor customer service other than maybe facebook.

• 
  John Kelvie (@jpkbst) reported 42 minutes ago

  @aronchick @QuinnyPig @awscloud If I was one of those hard-working Googlers, I would want this problem addressed so that people would be more likely to benefit from all my hard work and see the merits of it.

• 
  Matt Pegler (@matthewpegler) reported 44 minutes ago

  We're seeing DNS resolution issues in the east 1c AZ of AWS across multiple instances. Nothing on their status page yet. @awscloud

• 
  Kevin Kolk (@siberianmi) reported 45 minutes ago

  @matthewpegler @awscloud Had the same issue, it's us-east-1b in our account (use1-az4 zone id) forcing our DNS containers to avoid scheduling in that zone has fixed it for us (EKS)

• 
  Kevin Kolk (@siberianmi) reported 45 minutes ago

  @matthewpegler @awscloud Also the support tech on our ticket acknowledged it was an issue in AWS. #useast1 #aws #route53

• 
  Noah (@noahvelli) reported 45 minutes ago

  @disneyplus needs to pay for more @awscloud server usage on the days when it’s shows come out. The fact that I get kicked off the app 2-3 times on every premier day is infuriating.

• 
  AWS Blogs (@AWSBlogs) reported 47 minutes ago

  @awscloud … space lacking. They were either prohibitively expensive for an upstart, requiring a long term commitment upfront or the integration process was to be slow and painful, and they often relied on stale data for risk scoring that was not appropriate for certain target [2/3]

• 
  Ralf Büscher (@ralfbuescher) reported 51 minutes ago

  @QuinnyPig @amazonnews @awscloud I have the feeling in my gut, that a certain Jeff is really regretting to having given in on his desire to show his team how to solve problems and how to distract from other criticism. I think he hates himself now. Never mind, he will get over it.

• 
  John Gordon (@bluedonkey) reported 51 minutes ago

  Hmm, @awscloud, why does your EKS Cluster create flow use a default K8S version that is not the latest, then, once the cluster is finally active, show a message that an update is available. Fix the create cluster flow to use the latest as the default maybe?

• 
  Adriaan Bloem (@adriaanbloem) reported 53 minutes ago

  @AWSSupport Thanks. There's no solution for the problem I'm having (you can't choose hosted zone delegated name servers on Route 53) but it's good to know you're also paying attention to small individual users, not just the large corporate accounts :)

• 
  Rob Young (@bobbotron) reported 54 minutes ago

  The @awscloud cloudwatch metric tool is really quite good for the cost, but so frustrating if you want to drill down past the resolution it wants to show you. If want to get an export of the data? Forget it, which is super annoying if you're trying to get picky. :/

• 
  @Richi 😷 Jennings (@RiCHi) reported 55 minutes ago

  The self-styled #whistleblower alleges the firm only cared about its stock price ($UI). It led the market to believe the breach was the fault of a #cloud service provider, we’re told. But the insider says the actual problem was an insecure @AWScloud credential.

• 
  John Kelvie (@jpkbst) reported 58 minutes ago

  @aronchick @QuinnyPig @awscloud The bar is "don't turn off people's services for arbitrary reasons". Google is the only one I've run into this with, it's egregious (and feels much worse and different than, say, a Dynamo outage) and I'm fairly certain I'm not alone here.

• 
  Nas (@nasescobar316) reported 59 minutes ago

  @8HOUSE0 To build a social network, you first decide if you are going to use a Cloud Server or Your Own Server. If you build it with Amazon AWS, they can just shut you down like they did Parler. After that, you need very good coders, strict security on user data & money to start/scale.

• 
  Jen Hong (@the_jenhong) reported 1 hour ago

  You don't know pain until you try contacting @AWSSupport for urgent issues

• 
  tidyup (@tidyupmyworld) reported 1 hour ago

  @awscloud ...Hi Team, i'm unable to login to my root account and not receiving your call on my phone number, tried contact customer support but nobody seems to care...could you please help me out?