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:

• 
  Palestinian (@KhyzarKapoor) reported 2 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

• 
  Exodys (@711intern) reported 4 minutes ago

  /var/log/deoxys entry_019 / entry_020 (Weekend Edition) 1. Bug Hunting on a VDP > finished subdomain enumeration. > performed initial nuclei scan on the list, found some interesting things like CORS and subdomain takeover. > Used subzy tool to check for subdomain takeover, but all of those dangling subdomains pointed to amazon AWS elb so it was a dead end. > Also they fixed the CORS issue. > Started JS recon

• 
  RunTime | Engineering Recruitment (@lanceharvie) reported 10 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.

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

• 
  Shaaaaaaaaan (@AryavartKSamrat) reported 19 minutes ago

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

• 
  Nik Tiwari (@nikhil20077) reported 20 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.

• 
  Santhosh (@santhoshv) reported 22 minutes ago

  @PinokioSystem @AWSSupport But again health dashboard says forcast, but usage itself showing.. how come this is not explained correctly. Another point is it's the billing and money not any service down, so billing page itself could have add some alert

• 
  Drew Tewell (@drewtewell) reported 23 minutes ago

  @awscloud Is AWS having an outage?

• 
  Alex Hooper (@AlexHooper78640) reported 24 minutes ago

  @AWSSupport our entire system is returning 500s - what’s the eta on a fix for this?

• 
  Gerzson (@Gerzsononline) reported 25 minutes ago

  @slap__tjips @awscloud Gosh ai haters are so ******* dumb they just assume and blame it on ai for a funny error that didn’t result in any wrong

• 
  Thalapathy CCTV (@Chandrumakesha) reported 26 minutes ago

  @amazon @amazonIN @awscloud Hello sir My Amazon wallet not working, it's showing inactive, My wallet balance 4976 4 days gone still not working , iam suffering , for due amount what I do , please help me 8754825271 this number Already overdue going please 😔 help me

• 
  David Hinton (@DavidHinto48037) reported 27 minutes ago

  @awscloud @OpenAI Pop culture guru. Infuriatingly humble travel geek. Certified writer. Problem solver. paNs63

• 
  Silksteele (@silksteele) reported 31 minutes ago

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

• 
  Pratik Khasnabis ☁ (@softveda) reported 32 minutes ago

  Hey @AWSSupport your AWS Free Sandbox Environments launched with great hype doesn't actually start. Always gives an error code. Raised a ticket from builder support without any response so far. So much for the announcement.

• 
  Rudrakshya | Building Feedvoty (@RudrakshyaAi) reported 33 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.

• 
  Nikhil Raj (@nrworld121) reported 33 minutes ago

  @AWSSupport So you can send an alert email saying we owe you millions and create panic, but can't send a follow up that billing issues are going on. What a way to vibe code

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

• 
  the_chadman (@ChadmanThe) reported 37 minutes ago

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

• 
  YorkshireSarah (@SarahSWFC1867) reported 40 minutes ago

  @awscloud Customers want a working website / cloud. I'm hearing of a global outage of your systems. Any update? Thank you.

• 
  Koray Yersel (@korayyersel) reported 41 minutes ago

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

• 
  Arindam Sarkar (@asoptionsell) reported 41 minutes ago

  @awscloud AWS not giving me 1 year free server to run models.

• 
  Tiffa (@TiffaJessi) reported 42 minutes ago

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

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

• 
  Zoltán Szőgyényi (@zoltanszogyenyi) reported 49 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

• 
  GiveHateAChance (@HelpingHate) reported 50 minutes ago

  @awscloud It's cute how the ***** indians who caused all of this are never at fault and how you dismiss what a huge error this was with an emoji.

• 
  M (@mdw864) reported 54 minutes ago

  @AWSSupport I cannot login

• 
  Abdul Rauf (@armujahid) reported 56 minutes ago

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

• 
  Julley Thai (@julleybuilds) reported 57 minutes ago

  @kunalstwt @awscloud @FrancescoCiull4 rust is a steep climb but the compiler error messages honestly make it worth it once u get the hang of it

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

• 
  Jinam jain (@jinamcapital) reported 59 minutes ago

  Setting up a production-ready PostgreSQL cluster manually is painful. With @autobase_tech : -> Deploy a HA cluster in 10-15 minutes -> High-availability architecture, out of the box -> Works on @awscloud , GCP, Azure, Hetzner, DigitalOcean, or your own bare metal -> No manual setup. No guesswork. @PostgreSQL as a system, not a server.