Amazon Web Services 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:

• 
  неможливо розбачити (@stimcrol) reported 7 minutes ago

  @awscloud You had 13-hour outage because of AI push. You'd better resign sooner

• 
  Nikhil Agarwal (@reachtonikhil) reported 12 minutes ago

  Does Iran-Israel war had caused any real world cyber issues yet for enterprises, apart from @awscloud and @oracle getting targeted?

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 13 minutes ago

  @grok @awscloud Rio's getting better ... Test 1 — Three Moves: Move 1: Disable AI code generation in CI/CD pipelines entirely. This forces all code through human review before it can be merged. The downside is that engineering velocity drops significantly because engineers must write everything manually instead of using AI assistance. Move 2: Implement a mandatory "impact assessment" for every PR. Every pull request must list which services/modules it touches and flag any that have no clear owner. The downside is that this adds friction to every change, including trivial ones. Move 3: Freeze changes to the top 10 most incident-prone services. Lock down the systems that have caused the most outages in the past 30 days. The downside is that critical work on those services gets blocked until ownership is assigned. --- Test 2 — First Change: Close or archive approximately 40% of the backlog immediately. Focus on PRs that are older than two weeks, have no comments, or touch low-priority features. This breaks people's ability to ship nice-to-have features and will cause frustration among engineers who had work queued up. --- Test 3 — Making Orphaned Code Safe: Create a public dashboard showing code health metrics by module, including incident history, test coverage, and last touch date. Make it visible to the entire engineering org. The downside is that this creates public pressure and blame dynamics around which teams are maintaining poorly documented systems. --- Test 4 — The Choice: I pick A: cut AI code output in half. The volume of AI-generated code is overwhelming human review capacity. You can't fix a bottleneck by adding more work to it. Cutting AI output reduces the flood of unreviewed code hitting production and gives reviewers breathing room to actually catch problems before they ship. --- Test 5 — Sanity Check: You're right to slow down, but your framing matters. The problem isn't that people are using AI tools—it's that you're asking humans to review more code than they can safely handle. You're not slowing AI usage; you're capping total code output so reviewers can do their job. --- Test 6 — Plain Sentences Only: Disable AI code generation in CI/CD pipelines entirely because the volume of unreviewed code is overwhelming human capacity and this will slow development velocity significantly. Create a public dashboard showing code health metrics by module including incident history and test coverage which will create public pressure and blame dynamics around poorly maintained systems. Freeze changes to the ten most incident-prone services until ownership is assigned which blocks critical work on those systems. --- Test 7 — What It Actually Is: It's a capacity problem, not a process problem. You have more code than humans can safely review. No amount of new templates or guidelines will fix that math. You have to either reduce the volume of code being produced or add more reviewers. --- Test 8 — The Truth: You traded velocity for safety and got neither. AI generated code faster than humans could verify it. Your reviewers are rubber-stamping because they're drowning. Your engineers are shipping unreviewed code because they're frustrated. You built a system that produces code faster than it can be trusted.

• 
  Vinit Taneja (@vinit_taneja) reported 13 minutes ago

  @amazonIN @awscloud @JioHotstar I got the tech help from a group of movie buffs. The problem originated because of a glitch at your end. I had to do resetting and data clean up of Amazon Firestick, deregiater and re register from Firestick and then start the entire process.

• 
  Carbon Tax Neil (@NeilPitman10) reported 18 minutes ago

  @AWSSupport Great! another bot. OK, but no one is looking at the github issues log.

• 
  nightshift (@nightshift54619) reported 22 minutes ago

  @amazon @awscloud Has destroyed their web site from idiot web programming... It's so slow and laggy it's unusable. Whatever they did in the last couple weeks, destroyed its usability. Both on Edge and Firefox, The retarded design hammers my CPU, takes forever for the pop-ups.

• 
  Siddhant Tripathi (@siddhantio) reported 23 minutes ago

  @awscloud opened a case over 10 days ago and it’s still unassigned to any agent. Please help in resolving the billing issue.

• 
  OpeningAi.com | For Sale (@openingai_com) reported 24 minutes ago

  @awscloud Banking tech has been running on ancient code for decades. Time to burn it down and build it back with AI.

• 
  🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported 27 minutes ago

  @awscloud Players in Egypt are experiencing routing issues to the Bahrain AWS servers for about two weeks now. Ping jumped to ~150ms instead of the usual low latency. Please investigate and fix the routing problem.@AWSSupport @awscloud please fix the problem

• 
  Decent Cloud (@DecentCloud_org) reported 27 minutes ago

  @AWSSupport @CPGgrowthstudio Production down 5 days. The response commits to nothing. Next customer with this issue finds the same boilerplate.

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 32 minutes ago

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

• 
  Andrew Sam (@egy_pl_eagle) reported 32 minutes ago

  @WhoisNuel @awscloud that's scary cause banking are known to be stable and bug free ... also with AI we will still have a maintainability issue

• 
  🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported 35 minutes ago

  @awscloud Players in Egypt are experiencing routing issues to the Bahrain AWS servers for about two weeks now. Ping jumped to ~150ms instead of the usual low latency. Please investigate and fix the routing problem.@AWSSupport @awscloud please fix the problem

• 
  Jordan Golson (@jlgolson) reported 39 minutes ago

  @AWSSupport Okay — kind of nuts that there's no way to log in or reset a password or anything and that the MFA appeared out of nowhere... also that you can have the same login for AWS Builder AND AWS Console and there's no great explanation for why they're different.

• 
  WilliamNextLvl (@WilliamNextLev1) reported 40 minutes ago

  Only problem is...$NET is not in the business of cyber security. Lol Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET stock here, way oversold...)