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:

• 
  Saurbh Pandey (@JustABoyLost) reported 4 minutes ago

  @AWSSupport @AWSSupport The replies are coming too slow and my business is getting impacted coz of this

• 
  Eochu Ollathair (@TheDagda___) reported 6 minutes ago

  @awscloud Who do you want to be able to blame yourself or them? That is the decision. If you aren't confident in yourself, use them, but at the same time, maybe you are letting your customers down by not using the tools you have.

• 
  Astro Kanu (@AstroKanu) reported 7 minutes ago

  @awscloud @AWSSupport it’s a live project impacted - ur disrupting my clients- pls stop this casual approach and take this on priority- I am not able to login to my AWS account so I can’t access ur link - I’ve screen shots of all payments done which I can share resolve this now!

• 
  Hershal Rao (@Hershal0_0) reported 8 minutes ago

  @awscloud and here i am taking 3 business days to fix a single css bug

• 
  wojak'd (@ech3phr0n) reported 10 minutes ago

  @crypto_hades Yall paid shill retarded FUDders are obvious. How's @coinbase supposed to control an @awscloud outage?

• 
  akash (@akashtattva) reported 11 minutes ago

  i wonder whether anyone has ever mapped amazon AWS server costs to specific product feature improvements. because this kind of accounting framework being applied to ai spend seems intuitively wrong to me.

• 
  homanp (@pelaseyed) reported 14 minutes ago

  @0xMevu @specific_dev @awscloud It's a swarm of researches, we don't have issues with tool calls.

• 
  Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported 16 minutes ago

  I’m using @anthropic opus 4.8. With @awscloud Kiro. I have rules in my README that say only use Bash. But it ignored my instructions and said sorry I used Python after using a lot of tokens to do something I didn’t want it to do. I feel like I should get those tokens refunded: this is the kind of thing that unexpectedly wastes money and time and tokens unnecessarily. I can’t make the instructions any clearer. Stuff like that is so annoying. But I’m still writing code way faster. The problem is I got a $20 plan and used it up in a few hours. I tried switching back to 4.6 but seemed like the same results for code written. It’s like everything got more expensive after the new model showed up. Or maybe I really was just making that big of a change. I had to just up the subscription to $40. I’ve already spent a bunch of money on other subscriptions and got incorrectly billed $200 in tokens I couldn’t use this month (working on getting that refunded). So you can do the math. $40 per day x 31 = $1240. But people are using multiple agents. I could spin up an army of agents to write code for me if it didn’t cost so much. Who is going to win this game? As a single developer I’m seeking ways to reduce token usage (or whatever the billing metric is) and mistakes by agents like this one feel so unfair. It clearly was not what I asked for. Whether I fix it or the agent notices its mistake after the fact and fixes it without telling me it’s still going to cost the same. Bottom line is that I can produce a lot but it also costs me a lot and so far I haven’t found a way around that besides writing deterministic code. I have to get the thing built I want to make me money before I spend it all on AI tokens. But right now the agent is making mistakes and getting stuck on things I’m doing that I guess are unique and the agent hasn’t seen too much before. It writes code and can’t figure out what it did wrong, AWS shared networking with VPC endpoints and organizations delegated admins and such I’m getting around that (without giving up full access to my cloud account) by creating verification queries and code but then the agent doesn’t follow the existing file structure and uses the wrong language without at least asking…*sigh* Also it seems like the verification code is burning tokens like a wildfire out of control. Not sure how this is going to work out. I hope there’s not some issue like someone else siphoning off tokens behind the scenes or some other weird problem like the previous nerf issue.

• 
  Misu (@yngmisu) reported 17 minutes ago

  i’m having a really hard time getting better value from the open source models that are available on bedrock claude and codex just oneshot tasks, ending up cheaper in the long run i don’t like spending money on the model just solving compile errors in a loop @awscloud can we get some of the new models on bedrock or are yall busy with the openai deal (which i’m waiting for too)

• 
  Maroun Mourani (@MarounMourani) reported 19 minutes ago

  @AWSSupport account 608789101967 has 2 unassigned cases - one is 29 days old (cannot terminate EC2 instance - mec1-az2). The AZ outage prevent me from terminating an impaired instance and AWS keeps charging me. Can someone please look at this ?

• 
  Jason Sulano (@jmoney42777) reported 19 minutes ago

  @amazon @awscloud Run over my mailbox and drag this issue out for months with no resolution. Thanks Debashree Bose

• 
  chaturfier (@chaturfier) reported 20 minutes ago

  @AWSSupport Production AWS SES account paused over a resolved credential scrape. Keys rotated, issues fixed. Case 178014826500654 unread for over 48 hours while business halts. Help?

• 
  Abhijit Tripathy (@AbhijitTripat13) reported 20 minutes ago

  @AWSSupport @AWSSupport , when will they become agailable ? Its close to 14 hours now. 7 days and 14 hours ? This is what it takes to address an issue ?

• 
  Marci (@Nma_ci) reported 23 minutes ago

  @AWSSupport @AWSSupport @awscloud We are currently having an issue on our Production on AWS because a required quota is not being approved. This same quota was approved in our Test Environment on AWS. Support Ticket keeps getting closed. caseID: 177910350200072

• 
  Exchange Invest (@Exchange_Invest) reported 27 minutes ago

  Worrying times for @awscloud as various exchanges suffer another outage. More in today’s #ExchangeInvest.