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 (67%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Ciudad Jardín	Website Down	10 days ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 months ago
Point Pleasant Beach	Website Down	2 months ago
Little Rock	Errors	2 months ago
Atlanta	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:

• 
  Shaaaaaaaaan (@AryavartKSamrat) reported 6 minutes ago

  @Sahilvyas29 @JeffBezos @AWSSupport Its a amazon glitch man. Read about it.

• 
  ankur (@im__ankur) reported 7 minutes ago

  on my STUDENT account with a $10/month billing limit, I’m already unemployed & dead broke… and you drop $10 BILLION on me this month 😭 I can’t even afford ramen rn. Fix this glitch and throw in some credits for the mini heart attack pls @awscloud

• 
  Hector (@iamhectorlopez) reported 9 minutes ago

  @awscloud blocked my email from using their services again because i created an old account and never used it. I was supposed to enroll into a pay as you go plan. I've tried contacting them but i have just received template responses from them. Terrible support.

• 
  Kishan (@Kishan200615) reported 11 minutes ago

  @AWSSupport I have filled this form and it's been a month and In between I tried to contact to support and no use , Please Resolve this issue ASAP.

• 
  TheBlueDaisy (@diabendia) reported 12 minutes ago

  @mattsgarman @awscloud @amazon I’m having trouble getting my refund from Amazon, Matt! Please drop a name and phone number of someone who has the stroke to get this done!!

• 
  Pratikkumar​ Mohite (@DotSlashMohite) reported 14 minutes ago

  Spent this week breaking down @awscloud Regions and Availability Zones what they are, why they matter, how they work, where your app actually runs, and when to go multi-Region. Thread 🧵

• 
  jeff mayer (@jeffmayer) reported 19 minutes ago

  @AWSSupport @davidslosttt Your or the only one with trouble here, I got a disapproval for my application right out of the gate even though it met guidelines and I have used SES for another project for 5 years

• 
  Aaron Spiel 📣 (@SpielAaron) reported 19 minutes ago

  @AWSSupport It's not estimated. To quote the horrific emails you're sending people: "The month actual cost associated with this...". And yes, maybe it's easier to laugh and realise it's an error when you're potentially being billed $1,000,000,000. But when it's $80K, it feels scarily real.

• 
  Marek Serafin (@stoprocent) reported 21 minutes ago

  @DerDerDaIst @AWSSupport After they fix it, I'm setting up deny all policy.

• 
  Damon (@agaphto) reported 25 minutes ago

  @sorower01 @awscloud Also just got a $3m bill. There's an AWS issue going on

• 
  Soru Soran Adam (@SoruSoran_Adam) reported 27 minutes ago

  I felt really bad when I switched from Azure DevOps to AWS. Why did AWS create such terrible interfaces for DevOps / Dev Teams ? Constantly defining permissions with JSON is so tedious. It'll take a little while to get used to it. @awscloud @Azure

• 
  chetan soni (@chetansoni_it) reported 29 minutes ago

  @AWSSupport Same type of issue, occurred in my account as well

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

• 
  Mykyta (@mykytaso) reported 31 minutes ago

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

• 
  Head4Liberty (@Head4Liberty) reported 32 minutes ago

  @thewebbie @awscloud Especially cool that the rest of the month he’s projected to recoup ~$800MM. He needs to up his usage like crazy the rest of the month! (Not to mention many other errors and inconsistencies in that snapshot.)

• 
  Jyothish Nalinakshan (@GunnerJyo) reported 35 minutes ago

  @AWSSupport @AWSSupport Thank you for your response. I have already opened support cases 178395122100863 and 178395287500121 regarding this issue.

• 
  Drew Tewell (@drewtewell) reported 39 minutes ago

  @DoorDash Is there an @awscloud outage? #DoorDash isn’t working.

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 44 minutes ago

  @yellow_fellowz @awscloud @emm3122 AWS replied to me saying they’re aware of this issue

• 
  VarmıGol (@VarmiGol) reported 46 minutes ago

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

• 
  José Ramírez García (@joseramirezrk) reported 48 minutes ago

  @awscloud I'm sure no infra outage caused stress and had the same repercussions than this "issue" something must be done, I guess, no?

• 
  Goran Opacic (@goranopacic) reported 50 minutes ago

  @EIsenah @vercel @awscloud great post. keep pushing aws to fix stuff

• 
  Nik Tiwari (@nikhil20077) reported 53 minutes ago

  @awscloud Its been 22 days. My issues related acces to amazon bedrock is not resolved. I am frustrated with no help and arbitrary support. AI text generated is not help. Shameful @AmazonHelp #CustomerSupport #CustomerComplaint I replied in Dm nothing happened

• 
  Deep Value Memetics (@DV_Memetics) reported 54 minutes ago

  AI Morning Event Summary: softer ADP, but memory leads the pre-market unwind $SPY $745, -0.2% pre-market; $QQQ $732, -0.6%; $SOXX $632, -1.4%. The tape is opening with a memory-led AI-beta unwind even after ADP printed softer at +98k for June versus 120k est and 122k prior. ADP should help duration on paper, but semis are still lower into the 9:00am CT ISM Manufacturing release. For AI and semis, the opening read is de-risking first, macro relief second. $SNDK $2,168, -4.7% pre-market. BofA raised its price target to $2,500 from $2,100 and kept Buy, citing a NAND supply/demand imbalance through calendar 2027. implications: Street numbers are still moving higher, but the stock is giving back a crowded move into quarter-start trade. $MU $1,117, -3.2% pre-market. Barron's cited KeyBanc saying June DRAM pricing rose about 3% and NAND 2.4%, with limited new supply before 2027. implications: pricing data is still supportive, but the tape is digesting crowding and multiple risk after the recent run. $WDC $622, -2.6% pre-market. Storage is lower with the same memory unwind even after Cantor lifted its price target to $900 from $660 this week. implications: the open will test whether HDD / storage separates from NAND and DRAM again or just trades in the same factor bucket. $NVDA $199, -0.7% pre-market. Bloomberg and the Financial Times reported Taiwan widened the Super Micro server-export probe, keeping China server-channel scrutiny live. implications: no clean near-term estimate cut yet, but export-control enforcement remains an overhang for AI server channel names. $AMZN $240, +0.9% pre-market. AWS disclosed a new $1B Forward Deployed Engineering organization to embed thousands of AI engineers with customers. implications: higher near-term opex, but a clearer path to pulling Bedrock and agent workloads into production. Wall St one-liners $SNDK: BofA PT $2,100 -> $2,500, Buy -> firm expects NAND imbalance through CY27 and slower but still positive pricing into mid-2027. $MU: KeyBanc Overweight / PT $1,600, via Barron's -> June DRAM +3% and NAND +2.4% keep pricing up even as the stock de-risks. $WDC: Cantor PT $660 -> $900, Overweight -> AI storage demand and broader semi-cycle duration still argue for estimate support on pullbacks. 3 key tech headlines Anthropic / Commerce: export controls were lifted on Claude Fable 5 and Mythos 5, with access restoration starting Wednesday -> frontier-model supply and cloud demand debate turns back to product usage, not a forced outage. Google: Nano Banana 2 Lite ships with 4-second image generation at $0.034 per 1K images, and Gemini Omni Flash is now available to developers at $0.10 per second of video -> generative-media pricing pressure is still moving lower. Amazon AWS: the new $1B Forward Deployed Engineering push embeds engineers with customers to deploy agentic AI systems in days -> enterprise AI spend is moving from pilots toward implementation services and production workloads. What to watch - June ISM Manufacturing at 9:00am CT. The next macro gate is whether the post-ADP slowdown signal carries into factory demand and rates. - $QQQ / $SOXX after the open. Softer ADP did not stop the pre-market fade, so the first cash-session read is whether duration catches a bid or whether semis keep unwinding. - $SNDK / $MU / $WDC relative strength versus $SOXX. If storage still underperforms after fresh PT support, the move is more positioning than fundamentals. - $AMZN versus weak growth tape. Holding green on the AWS deployment push would keep enterprise AI implementation in focus. - $NVDA / server-channel headlines. Any additional Taiwan or export-control follow-through can keep pressure on AI server names even if the broader tape stabilizes. Sources: ADP National Employment Report; ISM release calendar; Amazon company release; Google blog; Bloomberg and Financial Times reporting; Wall St note recaps; live pre-market market data.

• 
  Kishan (@Kishan200615) reported 55 minutes ago

  @AWSSupport Please help resolve this issue as soon as possible, as I urgently need my AWS Associate certification. If you need any additional information, please contact me. Thank you.

• 
  PositiveVibes (@KPTheFighter) reported 57 minutes ago

  @awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws

• 
  Koray Yersel (@korayyersel) reported 58 minutes ago

  @AWSSupport My balance went down to zero. Time to the delete the aws account.

• 
  dale (@daleverett) reported 59 minutes ago

  @pkyanam @AWSSupport bro so its an error>???

• 
  ThriveCart (@ThriveCart) reported 59 minutes ago

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

• 
  ErisQT 💜 Hiatus (@ErisQT) reported 1 hour ago

  hey @EA @awscloud @EA_DICE fix your servers for dallas I'm having 80 latency

• 
  Mark (@MRRydon) reported 1 hour ago

  . @Cloudflare just opened the waitlist for its x402 monetization gateway. @awscloud shipped the same thing into CloudFront a couple of weeks ago. Any page, API, dataset, or MCP tool behind either of them can now charge an agent per request, settled in stablecoins - it's agent friendly commerce. The problem is simple. An agent that can research a trade but can't execute it, or produce work but can't get paid for it, is only half an economic actor. Closing that gap takes payment rails an agent can operate on its own, without a human clicking approve on every transaction. That's the same thing we're focused on at Aethir with Batch 2 and Aethir Claw. Our Batch 2 partners are building: a marketplace where agents complete work and settle with each other on-chain (OKX AI), a layer that gives an agent its own verifiable identity and lets it settle in stablecoins natively (Kite), gas-free rails so hosted agents can pay and get paid. Different entry point, same destination as what Cloudflare and AWS are doing at the edge. Agent commerce doesnt work until the payments work. Give an agent a way to transact and it becomes something that can operate with +EV. That's the layer the whole industry is building right now. We’re excited to be a part of it and to work with such amazing partners.