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:

• 
  Sadiq (@Md_Sadiq_Md) reported 55 seconds ago

  @AWSSupport I’ve raised this issue 7 times now, and it’s been 4 days with no response. I need someone to speak to ASAP

• 
  Arthurite Integrated (@Arthurite_IX) reported 1 minute ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  Thanh Nguyen (@ng_thanh8) reported 3 minutes ago

  @AWSSupport I really like Kiro, but let’s be honest — this is getting frustrating. It’s not the first time bugs and issues have shown up, and a lot of people have already reported them in Discord… only to be ignored or get no response. Being a fan doesn’t mean staying silent when support feels unresponsive. Hope the team starts paying more attention, because the community deserves better

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 5 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. 🧵

• 
  Perfect Enemy (@PerfectEnemy376) reported 6 minutes ago

  @AWSSupport I sent support requests two weeks ago, but there is still no solution to my issue! My problem is being completely ignored!

• 
  Siddhant Tripathi (@siddhantio) reported 10 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.

• 
  Decent Cloud (@DecentCloud_org) reported 11 minutes ago

  @AWSSupport @Mn9or_ User: cannot create a support case. AWS: create a support case. Problem solved - for AWS.

• 
  Corey Quinn (@QuinnyPig) reported 13 minutes ago

  @AWSSupport @0xdabbad00 Surely this time will fix it.

• 
  AI Tech News (@AITechNews_in) reported 16 minutes ago

  @amazon @AnthropicAI @awscloud 5GW = not scale… it’s dominance. AI is officially an energy problem now, not just a software problem.

• 
  Xyz (@Xyzfb2t) reported 16 minutes ago

  @awscloud First create a problem by having different services and the solve it by creating a new service.

• 
  Dhananjay Maurya (@dhananjaym182) reported 17 minutes ago

  @AWSSupport I have sent Aws case in private message please have look and fix the issue

• 
  zI£|~ (@Stunner_99) reported 18 minutes ago

  @AWSSupport I have an issue with the OnVUE exam I can't take a physical exam because of my schedule Now online option seems to be the worst It tells something unusual has happened each time it wants to launch my exam after going through alot of stress This is annoying

• 
  Adrian SanMiguel (@ar_sanmiguel) reported 19 minutes ago

  @ranman @QuinnyPig @awscloud Yeah, well. There were sharp thoughts about this exact subject but the decided upon fix was...double down on moar official engagement. It ain't exactly working.

• 
  Trevor Skinner (@PrometheusAIsec) reported 19 minutes ago

  I’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.

• 
  Mohamed (@abusarah_tech) reported 19 minutes ago

  i’ve recently went down a rabbit hole to learn how hyperscalers / cloud providers like @awscloud, @Azure (or at least in theory) work a huge respect to all the engineers that built the abstraction behind the resource provisioning. i am still trying to wrap my head around it