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 (53%)
• Errors (29%)
• Sign in (18%)

Live Outage Map

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

City	Problem Type	Report Time
Kyiv	Sign in	1 month ago
Chennai	Website Down	1 month ago
Point Pleasant Beach	Website Down	1 month ago
Little Rock	Errors	2 months ago
Atlanta	Website Down	2 months ago
Clearwater	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:

• 
  Ronald van Loon (@Ronald_vanLoon) reported 9 minutes ago

  Most AI pilots do not fail because the model is weak. They fail because the enterprise underneath it was never built for production AI. → Data volume → Latency → Deployment cycles → Legacy dependencies → Technical debt This is the infrastructure problem nobody is talking about. Sponsored by @awscloud. #AWSpartner

• 
  wokler (@wokler_) reported 9 minutes ago

  @awscloud It only took your servers doing down 3x as often to figure it out. good job.

• 
  Clint Jorgenson (@ClintJorgenson1) reported 11 minutes ago

  @AmazonHelp @amazon @awscloud The Customer Experience (CEx) company with absolute dismal CEx. Incorrect delivery notifications to customers is pathetic. Investigate this store and fix it.

• 
  Eduard Lugo (@eduardlh) reported 15 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.

• 
  Pranjal Agrawal (@agrawalpranjal7) reported 17 minutes ago

  @AWSSupport I am still waiting for an update from AWS, as it has been 13 days since I raised the issue, and it remains unassigned.

• 
  ich (@itsimeagain) reported 20 minutes ago

  @sundarpichai @sundarpichai A developer’s workflow isn’t linear. Ditch the €220 rigid barrier for the Ultra. Give us a $215/mo base + $50 rolling top-ups as collateral, rent NVL72/Rubin racks from @AWSCloud to fix capacity, and let us pay for real inference. Listen to the pros. 🚀 #GoogleAI

• 
  Amit Khera (@ai_amitkhera) reported 23 minutes ago

  @MatthewBerman They need not to fix other system vulnerabilities. They have to fix their system from its own. Now its clear that Amazon @awscloud is not secure as pretend to be. Now a clear risk is there when you are hositng your data in the system.

• 
  Kingdom of ElviSpeare (@ElviSpeareTV) reported 24 minutes ago

  All down: DoorDash. Spotify. GoDaddy. Verizon. Uber Eats. Amazon AWS. MLB Show. LinkedIn. Verizon. Microsoft Outlook. Ugh! Did someone cut the under water wires half way around the world?

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

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

• 
  Kishan Raj (@rajnahsik) reported 26 minutes ago

  @Im_IrushiK Same issue but @awscloud not fixing it.

• 
  ahmed (@ENGA999) reported 30 minutes ago

  @VodafoneGroup @awscloud @VodafoneBiz When does customer service in Egypt actually help customers? The app is terrible when it comes to roaming services. Every time I travel abroad, I struggle to activate or manage any service, and there are no real solutions. The only thing that works perfectly is charging customers

• 
  🍒Fᵣₑd ᵣₑᵣᵤₙ Cₕₑᵣᵣy🍒 (@SleazyWeez) reported 31 minutes ago

  @truestormyjoe @God999sdog @BB_Maguire Meta and Instagram are down. Amazon AWS is experiencing outages. All coincide with the time Tulsi dropped this declassified Intel. 🤔

• 
  Hershal Rao (@Hershal0_0) reported 31 minutes ago

  @awscloud anything to avoid hugging a server rack in a cold data center ever again

• 
  Nextwebb ⚡️⚡️ (@iam_nextwebb) reported 31 minutes ago

  @AWSSupport case 178287298000758 stuck on an account-verification hold since Jul 1. AI reply cited region-enablement, but actual error is "Blocked / account not recognized as valid". --dry-run succeeds, real launch fails. Can a human review? Happy to DM details.

• 
  Rohan Jeruel (@JeruelSingh) reported 31 minutes ago

  @AWSSupport @AWS Our AWS account has been suspended for 48+ hours. Production SaaS platform serving enterprise clients is down. Support case open but UNASSIGNED. We need a human at AWS Trust & Safety or Account Reinstatement to look at this TODAY. #AWS #AWSSupport

• 
  Funny Person (@PersonFunny23) reported 34 minutes ago

  @AWSSupport I don't use multiple case at a time I just use one case which case auto closed without resolving and without any reply . I already try to connect support team via call , chat , email not get response from support ,I am just wait and wait weeks are gone . So please resolve issue

• 
  the_chadman (@ChadmanThe) reported 36 minutes ago

  @AWSSupport the complaint is not only about login, it is also about money

• 
  Buttface (@buttface_9000) reported 43 minutes ago

  @sult @awscloud I mean, what are you trying to say? That they should double down on that or learn from their mistakes?

• 
  Wagecuck Liberator (@WagecuckR) reported 43 minutes ago

  @chainlink @amazon @awscloud Slow news day

• 
  Micah🦕 (@Tunes_TMz) reported 43 minutes ago

  @ApexLiveComms When sever update? @awscloud is terrible and clearly doesn't work.

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

• 
  Randall Hunt (@ranman) reported 46 minutes ago

  @pkyanam @QuinnyPig @AWSSupport Your account is probably flagged for fraud risk - any billing issues in the past? That's what seems to happen when people can't access the models automagically

• 
  Mykyta (@mykytaso) reported 47 minutes ago

  My server on @Hetzner_Online has been down for 7 hours and is still offline. Considering going back to @awscloud

• 
  ThriveCart (@ThriveCart) reported 47 minutes ago

  @TheWAHWoman Hello, Amazon AWS has triggered an unscheduled update, likely mitigating a wider issue on their end. This is impacting some carts. We expect AWS to resolve very shortly. We will provide an update when it does.

• 
  David Perlov (@DavidPerlov) reported 50 minutes ago

  @awscloud The company selling the compute says slow down. Noted.

• 
  1828 (@DEVELOPER1828) reported 50 minutes ago

  @AWSSupport my cognito users can sign up but require verification after sign up. if they close the verification page they are unable to sign in with the credentials they set. resetting password doesn’t work either, every code that gets sent to reset password is “invalid”.

• 
  Ventilateur sous couverture (@HugeVentilateur) reported 57 minutes ago

  @_JX14_ @irshit0 @awscloud This does not work as you expect. First ai is dumb, it can't remember things other months let alone years, second, it hallucinate, there is no fix for that yet. It also write convoluted code that "may" not work. Data leaks will exploded in the coming years...

• 
  Jesi_uhhduh (@DuhUhh38601) reported 60 minutes ago

  @IAGovernor @awscloud @Cognizant So much for fixing our water and farm land. You ******* suck. Spend money to research cancer in kids... Then add more cancer causing problems to the state that already has all the cancer by adding data centers. 👍🏼 Good job. Everyone clap for Kim she's so smart! 👏🏼 👏🏼

• 
  Intelfactor AI (@IntelFactorAI) reported 1 hour ago

  @awscloud More AI-Agents doesn’t make your revenue grow faster. It might actually slow you down.

• 
  Tanner Scadden (@TannerSDev) reported 1 hour ago

  @AWSSupport DMd. 19:27 we got the notice, saying take action by 06/22/2026. At 19:29 our production environment went down due to cloudflare being disabled. Please help us asap