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	9 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:

• 
  the_chadman (@ChadmanThe) reported 11 minutes ago

  @AWSSupport the complaint is not only about login, it is also about money

• 
  ThriveCart (@ThriveCart) reported 11 minutes ago

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

• 
  vasik mansuri (@vasik_mansuri) reported 17 minutes ago

  @AWSCloud @AWSSupport We've been waiting for support for more than 3 hours today and spent hours yesterday as well. Our account was suspended after a password reset issue. Password has been reset multiple times, support case updated repeatedly, but still no response.

• 
  Amit Khera (@ai_amitkhera) reported 19 minutes ago

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

• 
  Satyam Singh (@satyam147721667) reported 19 minutes ago

  @AWSSupport i submitted my problem , my acc is protected with mfa so idk whats happening it makes me scan qr or ask for a key to insert

• 
  RunTime | Engineering Recruitment (@lanceharvie) reported 19 minutes ago

  @AWSSupport I have a Basic Support billing case unassigned for 11 days. Two cards from two different banks are both being rejected by AWS at the merchant side. One bank confirmed in writing they approved the authorization, so this is not a card issue. I cannot pay my invoice.

• 
  Abhi Bavishi (@abhibavishi) reported 20 minutes ago

  Seems like a major glitch with @awscloud

• 
  Abdul Rauf (@armujahid) reported 21 minutes ago

  @miserer3_mei @AWSSupport It's a known issue that they are already checking

• 
  Ozan Yenidogan (@satori_11_11) reported 22 minutes ago

  seriously something wrong with @awscloud billing. always problem . @AWSSupport can you check please. case nr 178297207200499.

• 
  Ani (@nomad_on_run) reported 23 minutes ago

  @awscloud still the issue is not assigned. wow

• 
  naveen (@naveen4) reported 30 minutes ago

  we actually haven't been able to even use microvms yet since @awscloud is throttling our lambda quota to 8gb and has been extremely slow to assist. talk about 'customer obsession'

• 
  Zoltán Szőgyényi (@zoltanszogyenyi) reported 32 minutes ago

  @awscloud we've been waiting for over 10 days for a response on an issue that should have only taken 24 hours, per your description our company is registered on VIES for VAT in EU, yet you still charge us VAT when the reverse charge should be applied per EU law

• 
  Tiffa (@TiffaJessi) reported 33 minutes ago

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

• 
  Erin (@erinEncoded) reported 33 minutes ago

  @awscloud This is tone deaf. It wasn’t funny. It was upsetting. It reduced my trust in your systems, testing, and ability to roll back critical errors. I didn’t laugh. Why are you?

• 
  Marek Serafin (@stoprocent) reported 38 minutes ago

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

• 
  Drew Tewell (@drewtewell) reported 38 minutes ago

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

• 
  L'éclaireur (@apex_leclaireur) reported 40 minutes ago

  @luckychappy_ Only in your head, reality is they had a 6 year contract with a server provider and then switched to amazon aws servers. So your claims are bs. I studied computers and you dont understand anything. All battle royal games use 20hz servers that dont fail but your connection does

• 
  Wordy (@AnotherRadProd) reported 43 minutes ago

  @AWSSupport OMG... I was gonna have a heart attack! I haven't looked at this project for years and I can't even remember how to login!

• 
  Palestinian (@KhyzarKapoor) reported 48 minutes ago

  @AWSSupport Case 178428057900284 $100B billing error - went from $0.05 in S3 usage june 30th to billions overnight on July 1st Basic support plan but this is clearly system malfunction Need immediate help #AWSSupport #BillingEmergency

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

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

• 
  Jack Stone (@c0XhHxvylL) reported 49 minutes ago

  @stoprocent @AWSSupport when you owe aws 10k that's your problem when its 1 trillion it's their problem

• 
  Red Knight Capital (@Redknight8811) reported 50 minutes ago

  $VICR Why You Should Be Bullish! The AI Power Bottleneck Monopolist: Why $VICR is Day 1 Dominance We talk non-stop about AI chips and software, but we are completely ignoring the physical power crisis. Next-gen AI processors need an astronomical amount of electricity, and legacy power grids can't feed them. Enter Vicor Corporation ($VICR). Vicor isn’t selling commoditized hardware parts. They own the definitive technical solution to the AI infrastructure bottleneck: 48V Vertical Power Delivery (VPD). The Breakout Catalyst Checklist: 🔹 The Order Inflection: Bookings have absolutely exploded. Quarterly backlog surged a massive 70% sequentially to $300.6M on an insane 2:1 book-to-bill ratio. 🔹 Mid-Quarter Raise: Demand is scaling so fast that management raised Q2 revenue guidance to $142M—backed by a steep production ramp for lead AI giant Cerebras. 🔹 The Pure Margin IP Moat: Backed by historic legal patent victories, they’ve unlocked an high-margin licensing model projected to bring in up to $300M in pure royalty revenue through 2026. 🔹 Upgraded Corporate Target: Management just quietly lifted its long-term financial targets to a staggering $2.5B in revenue on an institutional-grade 70% gross margin. The Big Picture: If you want to link massive data center clusters to elite computing networks (like Amazon AWS, Microsoft Azure, or Nvidia accelerators), you must use Vicor's current multipliers to avoid melting the boards. The stock has ripped over 140% year-to-date for a reason. Are you holding abstract software valuations or locking down the actual power grid foundation of AI?

• 
  Slav (@slaviknowsbest) reported 52 minutes ago

  AWS is currently showing wildly inaccurate billing data in Cost Explorer. My $20 budget suddenly jumped to $30k+ (153k% over). Official incident: 'Inaccurate Estimated Billing Data' (Global) - started yesterday. Don’t panic yet - these appear to be display errors, not actual charges. Spread the word so others don’t freak out. #AWS #AWSDown #Billing @awscloud

• 
  SYED REHAN RIZVI (@SYEDREHANRIZV15) reported 54 minutes ago

  @awscloud @Experian That’s a significant transformation, cutting down that much time and effort. Smart use of tech to keep projects on track.

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

• 
  Silksteele (@silksteele) reported 59 minutes ago

  @adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.

• 
  Kingdom of ElviSpeare (@ElviSpeareTV) reported 59 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.

• 
  Dawid Pura (@puradawid) reported 60 minutes ago

  @AWSSupport @awscloud Please, before you will do anything else, can you just deploy a warning on cost explorer that those figures are inaccurate and there is an undergoing investigation? People seeing this can get into very big trouble because of fear, other emotions...

• 
  Zyreon (@Zyreon_trading) reported 60 minutes ago

  @awscloud When i wake up i saw:there is another AWS Bug/Service Down. Lol cannot give up time of 24 hours/7 days/infinity uptime..

• 
  paige s. (@PaigeSully88) reported 1 hour ago

  @awscloud Your AI sucks and costs more than humans. This sure is not a human error