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 (48%)
• Errors (35%)
• Sign in (17%)

Live Outage Map

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

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

• 
  Garratt Campton 🍄 (@gcampton) reported 3 minutes ago

  @AndrewChamb @awscloud It actually wasn’t able to do that, it could create new repos and PRs but not analyse and fix your own code. It would get downgraded. Sounds like you never used it.

• 
  Tanner Scadden (@TannerSDev) reported 5 minutes 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 cloudfront being disabled. Please help us asap

• 
  chaturfier (@chaturfier) reported 7 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?

• 
  Jyothi Venkat (@jyothiwrites) reported 14 minutes ago

  @awscloud Depends on the team. Junior devs copy pasting AI code? Disaster. Senior devs using it to skip boilerplate? Game changer. The tool isn't the problem, hows its used can be.

• 
  Catdingo (@CattManii) reported 18 minutes ago

  @awscloud Is that after or way after losing millions of dollars due to uptime issues?

• 
  Ameya (@lambatameya) reported 19 minutes ago

  @awscloud That's true for all software. More software can slow you down.

• 
  Charu (@Charu_Sethi) reported 20 minutes ago

  This week the same problem showed up in two places that don't talk to each other: Coinbase wrapping AI trading agents in an SEC-registered advisory, and x402 charging AI agents per request at the AWS edge. Both are solving authorisation-within-limits. Neither is interoperable with the other. Step back and the pattern is clear. Agentic settlement is becoming table stakes. x402 now runs through AWS CloudFront and WAF, settling USDC on Base and Solana via EIP-3009 in around 200ms, with 169M-plus cumulative payments. Mastercard's Agent Pay for Machines handles multi-rail M2M settlement. Coinbase is putting agent execution inside a registered wrapper. The rails are getting solved. What is not getting solved is the layer above them: a portable, revocable spending mandate that binds an agent's authorisation to a verifiable human or corporate entity and travels across rails. ERC-8004 gives agents identity and reputation, not spending authority. The agent-authorisation drafts (ERC-8118, 8184, 8150) are all single-principal or payment-channel scoped, and none has advanced. An agent authorised inside Coinbase's advisory and an agent paying through x402 at the AWS edge are governed by completely separate, non-portable models. That's the gap. The structural question worth testing: do the platforms each standardise their own proprietary mandate model, leaving on-chain rails competing inside someone else's walled authorisation garden, or does a neutral cross-rail mandate primitive finally emerge? Whoever ships the portable mandate owns the layer everyone else has to build against. @coinbase @awscloud @Mastercard #AgenticPayments #x402

• 
  1828 (@DEVELOPER1828) reported 22 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”.

• 
  Dude 3.0™ (@NamelessDudeZA) reported 24 minutes ago

  This is a real threat, WebAfrica was running their web hosting billing and support on WHMCS. So for the past few months WHMCS software has been under attack from hackers. My own server was attack through SQL injection of users fortunately I had to isolate and migrate to fresh new server provided by Amazon AWS.

• 
  Andrew Rodriguez (@andrewvr303) reported 27 minutes ago

  @Polymarket Glad I just got $10K in credits from @awscloud, hope it's made available on there quickly (still having issues getting Opus 4.8 to work, seems to be gated for whatever reason)

• 
  Jeff Grigg (@JeffGrigg1) reported 29 minutes ago

  @2fast2feeless @AlerixCodes @awscloud But also, you're 100% responsible for *FIXING* all the problems it creates, too! 😱

• 
  CHRISTOPHER BLAZ✨ (@Blaz_Dao) reported 30 minutes ago

  Walrus 🦭 and Walrus Memory explained in a lay man's understanding. Let's dive in: 1. What is" Walrus🦭" ?? Firstly, I want you to think of Walrus as a gaint decentralised hard drive built on Sui protocol or ecosystem. Walrus is trying to become the decentralized version of cloud storage services like Google Drive, Dropbox, or Amazon S3, but built for Web3. In a simple analogy, think of it like this; Google Drive vs Walrus With Google Drive, your files are stored on Google's servers and Google controls the storage. If Google removes a file or service, you're dependent on them. But, With Walrus🦭 it's a different case as your files are split into many pieces. Those pieces are stored across many independent storage providers in a cheap manner as no single company controls all of your data. And the most fascinating thing is as long as enough storage providers remain online, your files can be recovered whenever you want. 2. What is "Walrus memory"?? In plain English, Walrus memory is simply the storage space used to keep data on the Walrus network. That data can be:Images, Videos, Documents, NFT media, AI datasets, Website files, Backups etc. Why does it matter? Imagine a viral meme image on Sui. Normally, the blockchain only stores a reference to the image because storing the image itself would be too expensive. Most blockchains are good at storing transactions but terrible at storing large files. @WalrusProtocol is designed to store large amounts of data cheaply while remaining decentralized. ~BlazCares

• 
  Sentinet Radar (@Sentient_Radar) reported 33 minutes ago

  @awscloud Unvetted Slop will slow you down, make you crash and eventually compromise your data.

• 
  வல்லரசு (@VALLARASU_in) reported 35 minutes ago

  aws down? @awscloud

• 
  yapay zeko (@yesilliksepeti) reported 37 minutes ago

  @awscloud that is not an excuse of being behind ai race, it points a real problem of ai and its hype!

• 
  Tanner Scadden (@TannerSDev) reported 38 minutes 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

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

• 
  CCFC-New season (@sohali2012) reported 43 minutes ago

  @WNBA @awscloud Terrible stat.

• 
  CodeDodona (@CodeDodona) reported 46 minutes ago

  @awscloud From idea to revenue is not a technical problem.

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

• 
  Jinam jain (@jinamcapital) reported 49 minutes ago

  Setting up a production-ready PostgreSQL cluster manually is painful. With @autobase_tech : -> Deploy a HA cluster in 10-15 minutes -> High-availability architecture, out of the box -> Works on @awscloud , GCP, Azure, Hetzner, DigitalOcean, or your own bare metal -> No manual setup. No guesswork. @PostgreSQL as a system, not a server.

• 
  Ani (@nomad_on_run) reported 50 minutes ago

  @awscloud still the issue is not assigned. wow

• 
  angelmilkcry (@alina_aalx) reported 53 minutes ago

  @awscloud Maybe it’s your inability to adapt. You are used to development being a slow and manual process…that's how you sell more of your services

• 
  Tiffa (@TiffaJessi) reported 54 minutes ago

  Yo @awscloud u guys should totally idk maybe fix servers with @PlayApex because they’re TERRIBLE!!!!!!

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

• 
  Sid (@SidJain_80) reported 56 minutes ago

  @SahilExec Mistakes: CPU-heavy work in request blocks event loop Sync processing no scalability Local disk no durability / fills up App serves images no CDN Single server SPOF Tight coupling (upload = process = serve) Fix (at scale): Upload API store original in Amazon S3 push job to RabbitMQ async workers resize store back to S3 serve via Cloudflare

• 
  Randall Hunt (@ranman) reported 58 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

• 
  🇿🇦CN - Cracking News🇵🇹 (@walter_mashala) reported 59 minutes ago

  @awscloud @luis_usaa It’s good but will only server those who could afford using them, the world has more poor people than rich the people therefore it will work for the few.🤔

• 
  Matt Adams (@mattflashuk) reported 60 minutes ago

  @AWSSupport 40 days for a billing issue. Can you look into this please.

• 
  Zarroc.BTC 🧠 (@HuevaToi) reported 60 minutes ago

  @awscloud @OpenAI who else is just waiting for agentic ai to fix my budget woes?