Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
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 (50%)
- Errors (33%)
- Sign in (17%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Sign in | 30 days ago |
|
|
Website Down | 1 month ago |
|
|
Website Down | 1 month ago |
|
|
Errors | 1 month ago |
|
|
Website Down | 1 month ago |
|
|
Website Down | 1 month ago |
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:
-
Sentinet Radar (@Sentient_Radar) reported@awscloud Unvetted Slop will slow you down, make you crash and eventually compromise your data.
-
Kingdom of ElviSpeare (@ElviSpeareTV) reportedAll 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?
-
Rudrakshya | Building Feedvoty (@RudrakshyaAi) reported@AWSSupport Our AWS account was suspended due to a billing issue. We've now paid all outstanding charges, but our production SaaS is still offline. We have an active support case (#178295929600096). We'd appreciate any assistance in expediting the review. Thank you.
-
Piyush (@iPiyushKashyap) reported@awscloud Interesting take from the same company that built Kiro. Either AI-generated code is useful enough to invest millions in, or it slows teams down. Pick a lane.
-
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.
-
chaturfier (@chaturfier) reported@AWSSupport I was even just billed for this service that is now not working! Disgraceful!!! Distasteful! Sick! Fuckups!
-
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
-
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 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.
-
Jason Sulano (@jmoney42777) reported@amazon @awscloud Run over my mailbox and drag this issue out for months with no resolution. Thanks Debashree Bose
-
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 cloudfront being disabled. Please help us asap
-
Bull Theory (@BullTheoryio) reportedBREAKING: Snowflake $SNOW is up +40% today after crushing earnings and announcing a $6 billion deal with Amazon AWS. The stock had been down 20% in 2026 before this move, it just erased an entire year of losses in a single session. Revenue jumped 33% year over year to $1.39 billion, beating estimates of $1.32 billion. Earnings came in at $0.39 per share against expectations of $0.32. The $6 billion AWS deal spans five years and includes Amazon's Graviton chips and AI GPU infrastructure, locking Snowflake into the AI buildout as a core data layer. Snowflake is not even an AI company. It is the data infrastructure that AI runs on.
-
The Scambaiters (@TheScambaiters) reported@awscloud Thanks for your quick response to Nuking a Fraudulent PayPal Website, our other contacts shut down their Phones...
-
Andrew Rodriguez (@andrewvr303) reported@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)
-
Bryce Crawford 🐱 (@bryce_meow) reportedHave @awscloud service problem Contact AWS support "This response was generated using generative AI. You may need to verify responses." * Hallucinates * * Obvious mathematical error * Peak comedy
-
Astro Kanu (@AstroKanu) reported@aws @AWSSupport I’ve already used this link raised tickets explained the ongoing issue the only reply I got was pls log in- day 5 of my live project down- all payments made at my end- I’m serous if this isn’t resolved I’ll ask my clients to start contacting u for refunds #aws
-
Kingdom of ElviSpeare (@ElviSpeareTV) reportedAll down: DoorDash. Spotify. GoDaddy. Verizon. Uber Eats. Amazon AWS. Did someone cut the under water wires half way around the world? Possibly others.
-
John Mason 🐝 (@john_mason_) reported@wattreach @AWS @awscloud Good luck, AWS Support has been going down the tubes.
-
Unknown Man (@OPM2319) reported@awscloud @amazonIN @AmazonHelp Why is my package not yet delivered? ? And when will you ppl solve the issues ?? If its not delivered today its my last order with you guys .. pls look into the issue immediately
-
ProAmPete (@ProAmPete1) reported@AWSSupport @DiegooUA_ I am having the exact same issue, except support has inexplicably left my tickets in unassigned status for 3 months. I verified my identity and they in turn suspended and threatened to delete my account, and never even gave me the call I requested MULTIPLE times.
-
Hot_Tamales (@tama96420497) reported@IAGovernor @awscloud @Cognizant Terrible optics. Read the room.
-
Anna Singh (@anna_fanatic) reported@amazon @awscloud And shamelessly your team instead of rectifying have blocked my account. They didn’t bother to sort a small issue from your end the so called technical glitch just sent auto generated emails and blocked my email and twitter
-
Ameya (@lambatameya) reported@awscloud That's true for all software. More software can slow you down.
-
Astro Kanu (@AstroKanu) reported@awscloud @AWSSupport it’s been more than 4 days inspite of high billing cleared no access to my account nor able to login - live project disrupted- how are you resolving this ?? #aws
-
VarmıGol (@VarmiGol) reported@AWSSupport Hi @AWSSupport, thanks for prior help. Sent a DM about urgent Kiro issue still no human reply after days. Could you check and escalate please?
-
SpiritualTRADER (@Spiritual_Trad) reported@uditdwivedi079 @awscloud @AWSCloudIndia Because internet can be a problem. Once on cloud you don’t have to worry about it.
-
chaturfier (@chaturfier) reported@AWSSupport Correct: it's been just over 48 hours since the start of the issue.
-
Hershal Rao (@Hershal0_0) reported@awscloud anything to avoid hugging a server rack in a cold data center ever again
-
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.
-
oraclee.btc 🧠 (@oraclee_xyz) reported@awscloud @OpenAI but can it fix ****
-
Rohan Jeruel (@JeruelSingh) reported@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