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	1 day ago
Neuemühle	Errors	1 day ago
Rouen	Website Down	1 day ago
Noida	Errors	2 days ago
Noida	Sign in	4 days ago
Sydney	Sign in	8 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:

• 
  GioSteve Joestar (@StevenHinojosaF) reported 8 minutes ago

  @awscloud is it us or is CloudFront having issues? Seems to be failing randomly on us on certain locations. We already rolled out an issue with the server and seems to be pretty intermittent. Thoughts?

• 
  Eric Twilegar (@twiggyer) reported 9 minutes ago

  @awscloud 30 cents an hour for an sftp server, that still bills when it is offline. is aws transfer family some kind canary test of things to come. did some team just go off in left field and make their own pricing strategies. i'll just launch a t3 nano and install sftp.

• 
  DIVIJ SHAH (@therealdivij) reported 13 minutes ago

  Kya yaar tum logo ka server kitna slow chal raha hai. My EC2 instance has been running so slow for the last 2 days. @JeffBezos @ajassy @awscloud

• 
  Eric Swann (@eric_swann) reported 15 minutes ago

  @awscloud Looks like ECS/Fargate is having serious issues but your status is not reporting it. Any ideas? Our tasks just keep recycling and wont start up.

• 
  Ajeet Dhaliwal (@ajeetdl) reported 16 minutes ago

  @AWSSupport Internal server error (Service: AmazonDynamoDBv2; Status Code: 500; Error Code: InternalServerError; Request ID: VQH5NTAHPKKMKV5PFK9MV7Q4L3VV4KQNSO5AEMVJF66Q9ASUAAJG; Proxy: null) From the AWS DynamoDB Console (UI) when viewing tables. Hope this helps resolve the issue.

• 
  Jampy26 (Jacob Brinkley) (@Jamperl26) reported 18 minutes ago

  @AWSSupport is Amazon music down? I can't access/listen to the songs in my online playlists & it keeps giving me Service error message when i try to listen to songs

• 
  James Ford (@JamesRealTweets) reported 19 minutes ago

  @AWSSupport @gcollazo Are you guys still pretending this isn't an issue? Your status page still doesn't mention the significant issue with ECS

• 
  James Ford (@JamesRealTweets) reported 19 minutes ago

  @AWSSupport @tonyc Yes, same error here as well. The Service Health Dashboard is wrong. Please escalate

• 
  James Ford (@JamesRealTweets) reported 21 minutes ago

  @eric_swann @awscloud Yep, same issue here! The status page is very slow to update.

• 
  Ivonne Roberts (@ivlo11) reported 22 minutes ago

  What are some of your favorite web socket architectural designs on @awscloud? I'm starting a new project using API Gateway, web sockets and serverless @apollographql server to support subscriptions.

• 
  ali (@haaldem) reported 26 minutes ago

  @amiantos @elastic @awscloud woke up to the same issue yesterday morning, mine was also pinned to >=7.00,<8.0.0, and the docs kinda hinted at doing that for ES 7.x. Luckily it was caught by a daily deploy in the QA environment and avoided carnage in ****.

• 
  Ivica (@nekybrate) reported 28 minutes ago

  Hey @awscloud, could you improve error messages when an ECS task with placement constraints can't be placed? Seeing "The closest matching container-instance is missing an attribute required by your task" or even worse "ATTRIBUTE" when starting it from the CLI is not helpful. 1/2

• 
  Dr. Pratik Desai (@chheplo) reported 30 minutes ago

  @awscloud is ap-south-1 down? Can’t open URL from anywhere? All instances are down, too.

• 
  cellardoor 🍆 (@cellardogg) reported 32 minutes ago

  @AWSSupport @Jamperl26 EKS is down!

• 
  Paco (@Paco_S) reported 32 minutes ago

  @tonyc @AWSSupport Same here, we are experiencing an outage in all of us ECS deployments

• 
  prakashrajpoudel (@rajpoudel) reported 34 minutes ago

  @AWSSupport @tonyc We are getting same error for our ECS.

• 
  John Minnihan (@jbminn) reported 41 minutes ago

  @QuinnyPig @awscloud @dominos logs are delivered in 30 mins or your next outage is free

• 
  Jim Sykora (@JimSycurity) reported 42 minutes ago

  @QuinnyPig @awscloud @dominos This is a pretty big issue with Azure/M365 alerting also.

• 
  Eric Swann (@eric_swann) reported 44 minutes ago

  @awscloud @NatGeo Looks like ECS/Fargate is having serious issues but your status is not reporting it. Any ideas? Our tasks just keep recycling and wont start up.

• 
  AWS Blogs (@AWSBlogs) reported 46 minutes ago

  Excerpt: A challenge for many enterprises with data at the scale of petabytes is managing and taking actions on their data to migrate, improve efficiency, and drive down costs through automation. Amazon S3 buckets can hold billions of objects and exabytes of data, [1/2]

• 
  Angel Pizarro (@delagoya) reported 49 minutes ago

  @HPC_Guru @awscloud All credit should go to @koop_matt - the author who happens to be terrible at Twitter.

• 
  Felipe López (@FelipeLpez6) reported 49 minutes ago

  @tonyc @AWSSupport Same issue

• 
  Felipe López (@FelipeLpez6) reported 53 minutes ago

  @tonyc @AWSSupport Sale issue

• 
  Tony Cosentini (@tonyc) reported 54 minutes ago

  @AWSSupport is the ongoing outage also impacting Fargate? getting a "Timeout waiting for network interface provisioning to complete" error on every task launched over the past hour or so.

• 
  Kate Wathen-Dunn (@wd_kate) reported 55 minutes ago

  @AWSSupport @divinetechygirl @AWSSupport please please update your docs! Troubleshooting using docs with out-of-date or superseded functions is a frustrating waste of time. Ideally, I'd love to see docs/sections for general users and devs/setup separated for easier problem solving too. Thanks!

• 
  Neal O'Kelly (@NealOKelly) reported 56 minutes ago

  @AWSSupport If I may be so bold, the Service Health Dashboard rarely indicates issues. But nevertheless we know they happen.

• 
  Corey Quinn (@QuinnyPig) reported 1 hour ago

  @caseyrosenthal @CCBTRANSMISSION To my mind the revelatory breakthrough that @awscloud brought with FIS is simply being able to charge you 10¢ an hour for the outage.

• 
  hippy (@firsthippy) reported 1 hour ago

  Hi @AWS_UKI @awscloud Who thought it was a good idea to add a button click to add a CNAME to a Cloudfront? Why isn't this just a normal field like it was in the past? This change just slows users down.

• 
  Kris Kibwana Kivutha 😷🧼 (@Ngumbau) reported 1 hour ago

  Still having problems verifying my AWS account with @AWSSupport - 2 days in and still no resolution. I run the risk of losing $2000USD worth of sweet credits by Aug 08. Hopefully, it gets resolved but it is killing my momentum.

• 
  Jeremy Thomerson (@jthomerson) reported 1 hour ago

  @QuinnyPig @awscloud @dominos We literally had to add a message to the alert that says "remember that when you click this link to see the full event in CloudTrail, it won't appear for 15 minutes" because we kept forgetting that it's that slow. Thankfully CT publishes to EB instantly.