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	1 month 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:

• 
  Corey Quinn (@QuinnyPig) reported 5 minutes ago

  @AWSSupport @M0hkaif That’s not a great response. A. That place is a ghost town. B. Why not just suggest to the user that that’s expected behavior if they selected a multi-AZ cluster? It solves their problem right off.

• 
  Randall Hunt (@ranman) reported 6 minutes ago

  @pkyanam @QuinnyPig @AWSSupport Your account is probably flagged for fraud risk - any billing issues in the past? That's what seems to happen when people can't access the models automagically

• 
  Jyothi Venkat (@jyothiwrites) reported 10 minutes ago

  @awscloud Depends on the team. Junior devs copy pasting AI code? Disaster. Senior devs using it to skip boilerplate? Game changer. The tool isn't the problem, hows its used can be.

• 
  Kishan Raj (@rajnahsik) reported 11 minutes ago

  @Im_IrushiK Same issue but @awscloud not fixing it.

• 
  Buttface (@buttface_9000) reported 13 minutes ago

  @sult @awscloud I mean, what are you trying to say? That they should double down on that or learn from their mistakes?

• 
  M Si (@1210meh) reported 15 minutes ago

  @AWSSupport When can be fully recovered? My aws server working very slow

• 
  MarketMaverick (@MktMavPro) reported 15 minutes ago

  @RayT168 @nebiusai @awscloud But they are slow and usually die of a heart attack.

• 
  Jay (@jaycansea) reported 16 minutes ago

  @awscloud It slows everything down and is a disaster so far.

• 
  YorkshireSarah (@SarahSWFC1867) reported 17 minutes ago

  @tyaginikhil50 @awscloud I've just been told there is a global outage at the moment.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 18 minutes ago

  The 3-2-1 backup rule, applied to web hosting: 3 COPIES of your data 2 DIFFERENT storage types 1 OFFSITE location What this looks like in practice: Copy 1: Daily cPanel/WHM backup → stored on server Copy 2: Weekly backup → synced to Amazon S3 or Backblaze B2 Copy 3: Monthly snapshot → downloaded locally to your own machine Storage type 1: Server disk Storage type 2: Object storage (S3/B2) Offsite: S3 and your local machine are not on the same server The part almost nobody does: → RESTORING a backup to verify it works An untested backup is not a backup. It's an assumption. Once a month: → Pick a client site → Restore yesterday's backup to a staging environment → Confirm the site loads and the database is intact → Document the restore time If you've never done this, the first time you need it is not the time to find out it doesn't work. When did you last successfully restore from a backup?

• 
  참새 울음 소리는 칭어뤵뤵 (@20miracle17) reported 21 minutes ago

  @contemplena @BNBCHAIN @awscloud The onchain identity basically ties the agent's wallet and state to a unique address, so every interaction is verifiable and persistent across sessions without relying on a central server.

• 
  ThriveCart (@ThriveCart) reported 22 minutes ago

  @zenoix9 Hey, 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.

• 
  Peyton Nowlin (@Peyton_Nowlin) reported 26 minutes ago

  @Tech_Over_Lord @awscloud You are the problem so blindly anti AI you do not even understand the reference

• 
  Prince Raj (@theprinceraj) reported 29 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

• 
  DarkSoulja3323 (@DarkSoulja3323) reported 31 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

• 
  Red Knight Capital (@Redknight8811) reported 31 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?

• 
  IntelBull (@IntelBull_) reported 33 minutes ago

  $INTC is down nearly 30% from its all-time high. Just remember, analysts aren’t even counting foundry revenue in their estimates. If you wanted to jump into @Intel, now is the time to get in! I estimate the Amazon AWS 18A deal will bring $3 billion in revenue. I estimate the Microsoft custom 18A deal will bring $2 billion. Altera FPGA foundry deal: $2 billion Commercial defense & aerospace deals: $1.5 billion Apple deal: $5 billion Nvidia deal: $2 billion And more! More than $15.5 billion of revenue that will blow past analyst consensus and create a massive re-rating of Intel stock.

• 
  ProAmPete (@ProAmPete1) reported 33 minutes ago

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

• 
  None (@BourDeniz) reported 34 minutes ago

  @AWSSupport This is a production outage affecting a public API, website, and access to our primary research data store. The account contains irreplaceable research data! We need immediate account reinstatement or temporary read access PLEASE ! 178341882100620

• 
  Ordo Amoris ⛪️ 👩‍❤️‍👨👶👧🇺🇸🌎 (@OrdoAmorisVerus) reported 35 minutes ago

  @IAGovernor @awscloud @Cognizant This is a really bad decision. Indians only hire other Indians. You’ve put 200 Iowans out of work and given those jobs to H1b holders. Bad, bad move. Fix it.

• 
  Joseph Vita (@Joe__Life) reported 36 minutes ago

  @awscloud Because us-east-2 goes down

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

• 
  Kishan (@Kishan200615) reported 43 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.

• 
  SYED REHAN RIZVI (@SYEDREHANRIZV15) reported 43 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.

• 
  Drew Tewell (@drewtewell) reported 43 minutes ago

  @awscloud Is AWS having an outage?

• 
  Deep Value Memetics (@DV_Memetics) reported 44 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.

• 
  🍒Fᵣₑd ᵣₑᵣᵤₙ Cₕₑᵣᵣy🍒 (@SleazyWeez) reported 48 minutes ago

  @truestormyjoe @God999sdog @BB_Maguire Meta and Instagram are down. Amazon AWS is experiencing outages. All coincide with the time Tulsi dropped this declassified Intel. 🤔

• 
  Ameya (@lambatameya) reported 50 minutes ago

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

• 
  Andrew Rodriguez (@andrewvr303) reported 58 minutes ago

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

• 
  Rudrakshya | Building Feedvoty (@RudrakshyaAi) reported 59 minutes ago

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