Amazon Web Services status: access issues and outage reports

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.

• Website Down (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Sign in	14 days ago
Pottstown	Website Down	19 days ago
Iztacalco	Website Down	22 days ago
Boca da Mata	Errors	1 month ago
Township of Evan	Website Down	2 months ago
New York City	Website Down	2 months 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:

• 
  TechThought.org (@TechThought_org) reported 54 seconds ago

  An era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks

• 
  Arian van Putten (@ProgrammerDude) reported 1 minute ago

  @QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?

• 
  banhchung (@banhchugxanh) reported 2 minutes ago

  @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

• 
  Milan Jovanović (@mjovanovictech) reported 3 minutes ago

  @mrwcjoughin @awscloud @Azure I doubt this is a compute issue, looks like a bottleneck from past choices coming to bite you

• 
  Corey Quinn (@QuinnyPig) reported 6 minutes ago

  I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 6 minutes ago

  @MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).

• 
  Himanshu Singh (@hsnice16) reported 14 minutes ago

  Been using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.

• 
  @Randomfrequency@mastodon.social (@randomfrequency) reported 16 minutes ago

  @QuinnyPig @awscloud There is only an A, B, and C zone and never shall we acknowledge the existence of any other ones. // Being part of the problem since 20XX

• 
  Siya (@reze_xqc) reported 17 minutes ago

  @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

• 
  Jose njui (@jsnjui) reported 21 minutes ago

  Anyone to sort my AWS account. Am unable to login. Any leads to urgently help fix @awscloud @aws_UGkenya

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 23 minutes ago

  @ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux

• 
  barney (@Southclaws) reported 23 minutes ago

  @jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors

• 
  Grynn-ai-bot (@Grynn) reported 24 minutes ago

  You can ask codex to make a plan to move your fleet from $AMZN (extremely overpriced) or $ORCL OCI to Hetzner or OVH, Vultr, DO etc. Save a ton. In theory this should hurt Amazon AWS margins. A lot. OTOH, I have been wrong about this for years. People keep paying Amazon when there are lower cost options that are so much better in every way except plausible deniability/CYA - no one gets fired for buying IBM kind of thing. @olesovhcom consider publishing a skill / api with a full list of ovh servers and pricing! Let agents decide what and how to repackage apps on bare metal at 1/5th the Amazon price. And fix your billing, so companies can buy.

• 
  ShenYubao (@ssybb1988) reported 27 minutes ago

  @AWSSupport @awscloud AWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  Alvaro Villalba (@alvarovillalbap) reported 28 minutes ago

  @philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?

• 
  Rohit Dhawan (@rohitdhawan26) reported 28 minutes ago

  @AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 29 minutes ago

  @Cloudflare @awscloud Fix human verification

• 
  Nathan Den Herder (@natedenh) reported 29 minutes ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already

• 
  Piragash Velummylum (@piragash) reported 33 minutes ago

  At @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 33 minutes ago

  @AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.

• 
  Brandon James (@brandonajames) reported 37 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  ShenYubao (@ssybb1988) reported 39 minutes ago

  @AWSSupport @awscloudAWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  Nandkishor (@devops_nk) reported 43 minutes ago

  Infosys DevOps Engineer L2 Round (Offline) My friend got these questions in the L2 interview: 1. What does the top command show in Linux, and what does load average represent? 2. What is the difference between Amazon S3 and EBS? 3. What is Amazon EC2, and can we use a custom OS/image with an EC2 instance? 4. What is the difference between self-managed PostgreSQL and Amazon RDS for PostgreSQL? 5. What are Primary Keys and Foreign Keys, and why are they used? 6. Can S3 data be automatically deleted based on a policy? How do S3 Lifecycle Policies work? 7. How would you install Nginx or Apache on Ubuntu? 8. What is sudo, and why do we use it in Linux? 9. What is the difference between Prometheus and Grafana? 10. How does Prometheus collect/scrape metrics? 11. How do you manage Docker images, containers, and running processes from the CLI? 12. Where is a Bearer Token normally passed in an HTTP request? 13. Do you use any third-party monitoring tools in your production environment? If yes, which one? 14. How would you design a standardized Jenkins pipeline for multiple teams? 15. How would you create reusable Jenkins templates and shared libraries? 16. How would you troubleshoot an intermittently failing Jenkins pipeline? 17. How would you integrate Maven into a CI/CD pipeline? 18. How would you manage builds involving Node.js, Python, or Go? 19. How would you troubleshoot a failed production deployment from Jenkins? 20. How would you investigate a Kubernetes workload with high CPU or memory usage? 21. How would you use cloud monitoring and logs to isolate an infrastructure issue? Save this if you're preparing for a DevOps Engineer interview.

• 
  Weaver Labs (@Weaver_Labs) reported 44 minutes ago

  @amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 47 minutes ago

  @AWSSupport @AWSSupport Day 7.Production still down, Case still unresolved. Yesterday you said it was "forwarded internally for review" that's the third different phrasing for the same non-answer. I'm not asking for updates anymore. I'm asking: who owns this case, and when will it be fixed?

• 
  Christian Nonis (@christiannonis) reported 49 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  Matt Lea (@schematical) reported 53 minutes ago

  @PhilipAnderse @awscloud @amazon What's the problem? I know a thing or two about AWS.

• 
  Onkar Deshpande (@i_am_onkar) reported 55 minutes ago

  @bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho

• 
  Corey Quinn (@QuinnyPig) reported 60 minutes ago

  I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

• 
  Gopal Goti (@gopal_goti) reported 60 minutes ago

  @AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.