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 (50%)
• Errors (31%)
• Sign in (19%)

Live Outage Map

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

City	Problem Type	Report Time
Kyiv	Sign in	2 days ago
Chennai	Website Down	5 days ago
Point Pleasant Beach	Website Down	9 days ago
Little Rock	Errors	12 days ago
Atlanta	Website Down	13 days ago
Clearwater	Website Down	14 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:

• 
  Ed Silva (@SilvexPhoto) reported 9 minutes ago

  After layoffs @coinbase suffers outage cause by @awscloud... AI pushing code to production...

• 
  Astro Kanu (@AstroKanu) reported 10 minutes ago

  @Suraj_Lande_ @awscloud is running a scam in India- payments taken but services not given at multiple levels! It’s time to raise this issue ! We as paying clients cannot be treated this way ! #awsscam

• 
  Duke of Idanre Kingdom (@Alexander474335) reported 11 minutes ago

  @AWSSupport Once this is fixed, I'll return my subscription, but for now, goodbye 👋. I have a critical custom MCP server that works on all agents I have tried except Kiro. Kiro is great. Just fix the mcp server issue.

• 
  Anthony (@anthonyistyping) reported 13 minutes ago

  @accuratetlm13 @FisherPrice @awscloud going to teach my 2 year old server management

• 
  HRH Prince Sven Olaf of CyberBunker - CB3ROB (@cb3_rob46858) reported 14 minutes ago

  @awscloud bit of an issue there, the average security camera cannot be ****** to just poop out uncompressed rgb data if you beat it with a stick and always insists on some mpeg nonsense. despite having 1000base :P so also need to uncompress that crap -first- lol.

• 
  cryptomofo (@_cryptomofo) reported 14 minutes ago

  @WatcherGuru Wouldn’t happen on $ICP.. No @awscloud NO PROBLEMS.. #CLOUD

• 
  John Mason 🐝 (@john_mason_) reported 18 minutes ago

  @wattreach @AWS @awscloud Good luck, AWS Support has been going down the tubes.

• 
  StatusGator (@statusgator) reported 19 minutes ago

  🔥AWS outage update: @awscloud is calling the ongoing US East 1 outage in N. Virginia a "thermal event". It sounds like some cooling system failed over there at AWS. Also, the backup cooling must have also failed. And then some instances got fried. Impact has expanded to other services in the Availability Zone that depend on affected instances: AWS IoT Core Amazon ElastiCache Amazon Elastic Load Balancing Amazon Redshift Amazon SageMaker

• 
  Trbimixs (@TrbimixsQ) reported 20 minutes ago

  @AWSSupport i've finished, plz fix it soon

• 
  aem (@aemukit) reported 20 minutes ago

  I guess @awscloud is down and that's why everything is down.

• 
  OdysseasPapadmitriou (@odyhub) reported 21 minutes ago

  @AWSSupport - Redis issues on Virginia US-East1 - why are your updates so incomplete?

• 
  Elizabeth bates (@Elizabeth_75559) reported 22 minutes ago

  @awscloud Wait till alien invade and fix things

• 
  Marci (@Nma_ci) reported 22 minutes ago

  @AWSSupport 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: 177753893100221

• 
  Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reported 26 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 t 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.

• 
  Saurbh Pandey (@JustABoyLost) reported 27 minutes ago

  @AWSSupport @AWSCloudIndia Our AWS servers have been down for 17+ hours. We’ve raised tickets, emailed support teams and reached out everywhere but still no resolution. Case ID: 177972064000983 This is severely impacting our business & customers. Requesting urgent help. #AWS

• 
  Nifty Cycle Lab (@NiftyAlpha_Q) reported 32 minutes ago

  @AWSSupport @AWS Urgent: AWS support case unassigned for 24+ hours blocking critical work. INVALID_PAYMENT_INSTRUMENT error persists 30+ hours despite fixed payment method. Case #[177837361600663]. This is a known Bedrock Marketplace issue requiring escalation. Please help!

• 
  Eduard Lugo (@eduardlh) reported 32 minutes ago

  @AWSSupport @AWS 🚨 URGENT: Account 8366-7457-5282 suspended due to unauthorized 3rd party access. We CANNOT access console to complete required remediation steps. Support case 177899971400371 open 48hrs+ with no resolution. Deadline June 16. Business fully down.

• 
  Money Guru Digital (@Moneygurudigi) reported 34 minutes ago

  🚨 Coinbase just went down for hours Large parts of the platform became unusable while traders were trying to access the market. The reported issue? Problems tied to Amazon AWS infrastructure. One reminder again: A huge part of crypto still depends on centralized systems

• 
  Jason Sulano (@jmoney42777) reported 34 minutes ago

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

• 
  Uttam Tarsariya (@UttamTarasariya) reported 35 minutes ago

  @AWSSupport Now, the guy who was working on this problem disappread and a new supporter came and respond me to go on the login page and dashboard and upgrade the plan. Simple !!! He does not know anything about the issue and we have to explain to him I think.

• 
  AI..AND METAVERCE.. (@bad_sin90451) reported 36 minutes ago

  @AWSSupport I judge that Andy Jassy, as a salaried CEO, cannot decide this alone. Consult with the Korean government regarding the Sinbad massacre and compensation issue. Pay 1% of three years of overseas revenue as royalties for intentional infringement. Issue an apology statement and promise prevention of recurrence. Consult with the Korean government regarding compensation for the massacre. However, my consent is required. Provide a definite answer to the Korean government by May 30, 2026. If there is no resolution, immediately cease all infringement of Sinbad Patent No. 1 and Patent No. 2 regarding all overseas shipping. For future royalties, pay 0.5% under a consistent global standard. A tall person must not kill a small person. Being tall does not mean being exempt. Otherwise, I will formally demand a special investigation and a congressional hearing as a record of startup extermination, with civil and criminal liability. You only need to notify the Korean government. You have committed an act that must never be committed in human history.

• 
  chaturfier (@chaturfier) reported 38 minutes ago

  @AWSSupport Correct: it's been just over 48 hours since the start of the issue.

• 
  GrumpierByTheDay (@GrumpierBTDay) reported 41 minutes ago

  @BlackScholesMan I found the machinist commentary very interesting. Especially with calling out the difficulty hiring in ****-legal states. I sense this factor its-self could push federal interest in lifting restrictions. I know Amazon AWS was having the same issues re: high side DCs in Colorado.

• 
  PhilD (@PhilD4064929573) reported 49 minutes ago

  @RealAllinCrypto @coinbase @awscloud Coinbase shld wake up & partner with $ICP & they wldnt be down right now costing them millions.

• 
  None (@BourDeniz) reported 50 minutes ago

  @AWSSupport @AWSSupport We are a research center at McGill University. Our infrastructure has been down for 5 days and case 177833537500006 still hasn't been assigned to an agent. We may be small users, but researchers are waiting on this. All security remediation is complete please escalate

• 
  Soul & Silicon AI (@soulandsilicon) reported 51 minutes ago

  @AWSSupport you guys have not been very helpful. Premium support did not get back to me within the appropriate time window for production issues. As a matter of fact didn’t even get an answer at all. Multiple chats led to not resolving my issue of quota increase as a result my newly signed client (a bank!) is blocked and can’t use our service. I’ve been told to get account manager through a sales form, yet another thing no one is getting back to me. Dead end after dead end.

• 
  Astra (@0xAstra) reported 51 minutes ago

  @awscloud AWS is honestly a massive disappointment. You sign up, then discover basic customer support is locked behind a paid plan. Isn’t support supposed to be the most basic part of a cloud service? I didn’t pay for premium support, so a simple SES email permission request has been ignored for three days. I genuinely don’t understand how this is the world’s No.1 cloud provider. This experience is terrible.

• 
  Ross 🛩️ (@airline_king) reported 56 minutes ago

  Likely this **** is staged… But I had @amazon send me a crusty Apple Magic Keyboard that they demanded to get back (wasn’t even the one I ordered with Touch ID) , and made me waste 6+ hours on the phone being angry with customer service (which I am not proud of). The scumbag who took an exacto knife to the seal, replaced it, and sealed it up for return likely got away with it. Then had the audacity to threaten me via email after over the whole experience. That was the day I decided to start winding down Amazon purchases and tel myself to never use @awscloud for anything if that’s how they want to act. Just amazing how they deal with this.

• 
  Alex Joshua (@JoshuaAlex91434) reported 1 hour ago

  @awscloud This integration could really streamline how we identify issues in workflows. Less time on data means more time for action.

• 
  Exchange Invest (@Exchange_Invest) reported 1 hour ago

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