Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".
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.
At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!
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:
-
Amit Khera (@ai_amitkhera) reported@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.
-
MarketMaverick (@MktMavPro) reported@RayT168 @nebiusai @awscloud But they are slow and usually die of a heart attack.
-
Jay (@jaycansea) reported@awscloud It slows everything down and is a disaster so far.
-
🇺🇸 End H1B F1 OPT TN E3 O1 L1 I1 H4 all NIV 🇺🇸 (@slmimorgan) reported@IAGovernor @awscloud @Cognizant You need to stop down you treasonous monster. You are elected to serve we the American people. Not Cognizant or Indians. Shame on you.
-
HR Toby bookmarking everything (@TobyfromHR69) reported@IAGovernor @awscloud @Cognizant This is terrible. You aren’t Iowa First. They under bid the project. You save some money and Indians with fake degrees get Iowans jobs. Terrible terrible legacy move.
-
DIWhyCoder - ⌨️ 🇺🇸 (@diwhycoder) reported@awscloud AWS running out of server space confirmed.
-
Prithvi Jadwani | AI SEO | GEO | REDDIT SEO | GMB (@Prithvi_Jadwani) reported@aselipsky @awscloud 15 years is a long time to spot the same bottleneck. What's the fix for hyperscalables now, then?
-
Sentinet Radar (@Sentient_Radar) reported@awscloud Unvetted Slop will slow you down, make you crash and eventually compromise your data.
-
Ahmed Fouad (@ahmedfouaddev) reported@awscloud Yeah, because it takes much more time to debug and find issues later...
-
Satyam Singh (@satyam147721667) reported@AWSSupport wait , i didnt login for 90 days , does that mean my acc is permanently closed ?
-
Catdingo (@CattManii) reported@awscloud Is that after or way after losing millions of dollars due to uptime issues?
-
Just Le Canuck 🌸👹 (@JustAGamer6464) reported@awscloud No duh. Especially when you don't have people capable of actually analyzing the code for issues before deploying it. Operating under the "fix it later" instead of running QA. And maybe actually hire American programmers.
-
Teri Radichel #cybersecurity #pentesting (@TeriRadichel) reportedI’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.
-
Charu (@Charu_Sethi) reportedThis 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
-
Glen Wilson (@GlenWilsonIA) reported@awscloud Amazon existing. You should shut down and donate your assets to charity.
-
Corey Quinn (@QuinnyPig) reported@BillJelavich @nearyd @awscloud If you're having fencepost errors, I feel bad for you son; I've got 99 problems and somehow solved one hundred one.
-
AI Inc (@AiTesty5) reported@awscloud Normal people call this „skill issue“… come one AWS, you’re selling us this crap and then talk bad about it?
-
Deepak (@thedeepflux) reported@awscloud fwiw, saw AI-generated code slow a single dev by 20% initially due to more time spent verifying than writing. after adding pair programming checkpoints focused on trust-building, velocity normalized. AI isn’t a speed hack; it demands a new craft layer with review discipline.
-
Hershal Rao (@Hershal0_0) reported@awscloud anything to avoid hugging a server rack in a cold data center ever again
-
Jesi_uhhduh (@DuhUhh38601) reported@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! 👏🏼 👏🏼
-
Exodys (@711intern) reported/var/log/deoxys entry_019 / entry_020 (Weekend Edition) 1. Bug Hunting on a VDP > finished subdomain enumeration. > performed initial nuclei scan on the list, found some interesting things like CORS and subdomain takeover. > Used subzy tool to check for subdomain takeover, but all of those dangling subdomains pointed to amazon AWS elb so it was a dead end. > Also they fixed the CORS issue. > Started JS recon
-
Clint Jorgenson (@ClintJorgenson1) reported@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.
-
Matt Adams (@mattflashuk) reported@AWSSupport 40 days for a billing issue. Can you look into this please.
-
Tanner Scadden (@TannerSDev) reported@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
-
oraclee.btc 🧠 (@oraclee_xyz) reported@awscloud @OpenAI but can it fix ****
-
Tiffa (@TiffaJessi) reportedYo @awscloud u guys should totally idk maybe fix servers with @PlayApex because they’re TERRIBLE!!!!!!
-
David Perlov (@DavidPerlov) reported@awscloud The company selling the compute says slow down. Noted.
-
yapay zeko (@yesilliksepeti) reported@awscloud that is not an excuse of being behind ai race, it points a real problem of ai and its hype!
-
Buttface (@buttface_9000) reported@sult @awscloud I mean, what are you trying to say? That they should double down on that or learn from their mistakes?
-
chaturfier (@chaturfier) reported@AWSSupport Correct: it's been just over 48 hours since the start of the issue.