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 (46%)
• Errors (35%)
• 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	20 days ago
Chennai	Website Down	23 days ago
Point Pleasant Beach	Website Down	27 days 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:

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

  All down: DoorDash. Spotify. GoDaddy. Verizon. Uber Eats. Amazon AWS. Did someone cut the under water wires half way around the world? Possibly others.

• 
  AI..AND METAVERCE.. (@bad_sin90451) reported 4 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.

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

  aws down? @awscloud

• 
  Astro Kanu (@AstroKanu) reported 12 minutes ago

  @awscloud @AWSSupport if u don’t resolve this on urgent basis I’m going to start telling my clients who have paid for my services- which are down because of you to start writing to u to claim a refund - you cannot disrupt a live project and be so causal about this #aws #awsscam

• 
  Duke of Idanre Kingdom (@Alexander474335) reported 14 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.

• 
  Jared Scheel (@jscheel) reported 14 minutes ago

  Hey @AWSSupport, I have filed a business critical issue and your support system is consistently failing. Every time the call comes through, your system says it experienced a technical issue connecting us and you are now outside your SLA for responding.

• 
  Joyfulwood (@JoyfulWood) reported 15 minutes ago

  $GXAI 1.47 Dip SL under 1.39 Ran big on news this morning, brought down to support at 1.45. Trying for a second run. PT 1.75/1.89/2/2.15/2.3+ Gaxos Secures Additional Funding from Amazon AWS to Accelerate AI Sales Platform Development

• 
  Charu (@Charu_Sethi) reported 16 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

• 
  dolla bill (@BillBah) reported 16 minutes ago

  @IAGovernor @awscloud @Cognizant Cognizant is a terrible company. The “savings” will cost more in the long run.

• 
  Jason Sulano (@jmoney42777) reported 17 minutes ago

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

• 
  Deepak (@thedeepflux) reported 21 minutes ago

  @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.

• 
  Prince Raj (@theprinceraj) reported 31 minutes ago

  @vansh22b @awscloud @AWSCloudIndia Contact them through support email. Explain to them your problem and that you cannot afford to pay this bill. They often waive off the bill when you leave a VPS or paid service running mistakenly

• 
  Ahmed Fouad (@ahmedfouaddev) reported 32 minutes ago

  @awscloud Yeah, because it takes much more time to debug and find issues later...

• 
  Andrew Chambers (@AndrewChamb) reported 33 minutes ago

  @awscloud Definitely Amazon raising dubious concerns to the US government for weak reasons like being able to fix bugs.

• 
  Rudra Narayan Mohapatra (@rnmohapatra46) reported 33 minutes ago

  @awscloud Hi, I took the AWS Certified Solutions Architect – Associate exam about 3–4 weeks ago, but my digital badge is still not showing up on Credly. Could you please help me resolve this issue? Thanks in advance.

• 
  Sentinet Radar (@Sentient_Radar) reported 35 minutes ago

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

• 
  Sridhar Katakam (@srikat) reported 41 minutes ago

  @AWSSupport 39 hours since my email reply and still waiting. There's not a single human reply so far regarding the billing issue.

• 
  wokler (@wokler_) reported 47 minutes ago

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

• 
  Hershal Rao (@Hershal0_0) reported 48 minutes ago

  @awscloud finally, i can keep my embarrassing "fix later" comments strictly internal.

• 
  Astro Kanu (@AstroKanu) reported 49 minutes ago

  @awscloud @AWSSupport you need to give me an e mail address to write to as I’ve no option to log into AWS as your team has deactivated my account. Now it’s time to take this issue seriously as I’ve been raising it patiently for 36 hours while my live project is disrupted

• 
  Ventilateur sous couverture (@HugeVentilateur) reported 50 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...

• 
  DarkSoulja3323 (@DarkSoulja3323) reported 51 minutes ago

  I had this exact problem with a Oled monitor i ordered @amazon @awscloud . Fix your **** Amazon!!! Have severe punishments for these people so they never do this ****. The driver got out with my orderer, and just got right back in the van. I said what are you doing? He said, i have to go pee so i was in a hurry? Wtf kind of Bullshit excuse is that while delivering something for someone thats %600

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

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

• 
  Shawn Jots (@shawnjots) reported 52 minutes ago

  @awscloud been trying to create an account over 36 hours ago but I realized your sign up process is broken. Getting this error: response: { "message": "Failed to start DIVA SMS PIN verification".... Can you help?

• 
  Rohan Jeruel (@JeruelSingh) reported 54 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

• 
  Hot_Tamales (@tama96420497) reported 55 minutes ago

  @IAGovernor @awscloud @Cognizant Terrible optics. Read the room.

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

• 
  Ameya (@lambatameya) reported 58 minutes ago

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

• 
  Eduard Lugo (@eduardlh) reported 59 minutes ago

  @AWSSupport Hi @AWSSupport, 🚨URGENT: Is there anything else I can do to expedite this process? A phone number I can call, or an email address? My business has been down for 48 hours. Please advise.

• 
  Arroiss (@arroiss12) reported 1 hour ago

  @felipestscosta @AWSSupport I'm having the same problem and AWS isn't giving me a proper response. I'm losing a lot of money because my services stopped without prior notice. @AWSSupport