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 (63%)
• Sign in (19%)
• Errors (19%)

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

• 
  Marvelous Ikechi (@IkechiMarvelous) reported 1 minute ago

  @awscloud I’m guessing this was the admins last day at work. He won’t be going down without a fight.

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

• 
  Tanner Scadden (@TannerSDev) reported 9 minutes ago

  @AWSSupport DMd. 19:27 we got the notice, saying take action by 06/22/2026. At 19:29 our production environment went down due to cloudflare being disabled. Please help us asap

• 
  ErisQT 💜 Hiatus (@ErisQT) reported 9 minutes ago

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

• 
  Ordo Amoris ⛪️ 👩‍❤️‍👨👶👧🇺🇸🌎 (@OrdoAmorisVerus) reported 16 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.

• 
  Vivek Varia (@vivekvvaria) reported 18 minutes ago

  Not able to login, I am planning to register for AWS Certified Cloud Practitioner. @awscloud

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

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

• 
  Alex Hooper (@AlexHooper78640) reported 32 minutes ago

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

• 
  AntDracula (@ant_dracula) reported 33 minutes ago

  @leeman24 @GyuMusang56418 @awscloud They don’t need sloppers. They need people with deep knowledge of their products, not slop cannons taking down entire regions. They laid those people off and now it’s an outage every other week, with worse support.

• 
  David Hinton (@DavidHinto48037) reported 35 minutes ago

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

• 
  Rich Peter (@peterli34923561) reported 35 minutes ago

  $AAOI --- In late March and early April, $AAOI issued consecutive announcements revealing it had won a massive $71 million new order for 800G single-mode optical transceivers from a top North American internet giant (widely speculated to be Amazon AWS or Microsoft). Critically, management confirmed the first batch of 800G products entered volume shipment in Q1, marking the company's official entry into the world's highest-end AI optical communications supply chain. On April 17, $AAOI announced it will expand its manufacturing footprint to 900,000 square feet in Pearland, Texas via acquisition and leasing of adjacent facilities. Exiting Q1, its 800G transceiver monthly production capacity reached 100,000 units — this expansion is explicitly built to meet exploding order demand from AI customers. On April 29, the State of Texas awarded $AAOI $20.85 million in semiconductor innovation fund grants to support its domestic advanced photonic chip manufacturing in Sugar Land. This not only eases significant R&D and facility buildout capital pressure, but also underscores its strategic position in the U.S. domestic manufacturing ecosystem. 1. The Ultimate AI Compute Bottleneck: The Copper-to-Optical Upgrade (800G / 1.6T) Global data centers are currently undergoing a generational upgrade supercycle, shifting from 400G to 800G and even 1.6T optical transceivers. AAOI is one of the most direct beneficiaries of this hardware refresh cycle. As AI chip compute power from giants like NVIDIA grows exponentially, traditional copper transmission can no longer support the massive, ultra-high-speed data exchange required inside hyperscale data centers. Optical transceivers — devices that convert electrical signals to optical signals — have become the critical throughput bottleneck for AI server clusters. 2. Vertical Integration Breaks Gross Margin Ceilings Unlike many transceiver vendors that only perform final assembly, AAOI has in-house R&D and manufacturing capabilities for photonic (laser) chips. Competitive advantage: Amid industry-wide supply shortages, owning upstream chip capacity means no supply bottlenecks. And as scale effects kick in from higher shipments in H2, its previously criticized high fixed costs will be heavily diluted, with Non-GAAP net income expected to swing rapidly to profitability in Q2 and Q3 this year. 3.3. Dual Engine Growth: CATV Broadband + Data Center Beyond AI data centers, AAOI's legacy stronghold — cable broadband networks (HFC/CATV) — is also entering a cyclical recovery. On May 12, the company announced a deep partnership with U.S. broadband giant Mediacom to roll out its full DOCSIS 4.0 network upgrade program. This stable legacy business provides a solid base of recurring, predictable cash flow.

• 
  Exodys (@711intern) reported 37 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

• 
  Alex 🇨🇦 (@leeman24) reported 37 minutes ago

  @ant_dracula @GyuMusang56418 @awscloud I will agree on support falling off for their neglected services. Any time I interact with Textract/Comprehend support, they take 1+ hrs to join the chat and my issue is always a bug they got to reach out to the product team for. I also agree senior engineers will be good at AI.

• 
  Ani (@nomad_on_run) reported 39 minutes ago

  @awscloud I raised this unblock quota reqst on 9th, today is 16th. I really don’t know if ur policy is to deliberately frustrate a customer so that he buy a support plan, bcoz unblocking a quota error is not a heavy task at all. Let alone solving, u haven’t assigned anybody yet

• 
  Corey Quinn (@QuinnyPig) reported 39 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.

• 
  Aadit Rai (@aaditrai) reported 40 minutes ago

  Mike Brown has class and respect for his people, so I will say it. The NBA lacks integrity for the sport. Allowing an environment that allows playing keep away as a fundamental part of a close game is ridiculous. Allowing players to get away with literal physical assault and not calling anything is wrong. Champagnie kicks his feet out after the ball has released from his hands and Jalen Brunson gets a flagrant! That being said I will be doing a full break down on the publically posted highlights tomorrow, Fair Use. @nba @ajassy @awscloud Go Knicks!

• 
  Soru Soran Adam (@SoruSoran_Adam) reported 45 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

• 
  vars molta (@D_Kahinga) reported 46 minutes ago

  can china do the same for google, amazon aws, claude, and nvidia? and what would be the problem with that?

• 
  Matt Adams (@mattflashuk) reported 46 minutes ago

  @AWSSupport 40 days for a billing issue. Can you look into this please.

• 
  Ben (@ben_codez) reported 48 minutes ago

  @vijaytupakula @pushpak1300 @awscloud Problem is SES never approve me out of the sandbox and literally don’t tell me why. 🤷

• 
  prakash Kumar (@Kumarprakash03) reported 49 minutes ago

  @awscloud @awscloud I say ok don't worry you will deliver tomorrow. But some days i was watching amazon only provide date but he was not giving my product when orderd hai Then I canceled that order because amazon didn't give the any response of my problem and I ordered again.

• 
  Pratik Khasnabis ☁ (@softveda) reported 50 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.

• 
  wokler (@wokler_) reported 50 minutes ago

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

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

• 
  Miguel A. Vega Segovia (@mavegasegovia) reported 51 minutes ago

  @AWSSupport @AWS URGENT: my AWS account 268140507056 has been WRONGFULLY SUSPENDED for ~48h — AFTER paying my invoice IN FULL (balance $0.00). My 100% digital business is completely DOWN, losing customers by the hour. 🧵

• 
  Garratt Campton 🍄 (@gcampton) reported 52 minutes ago

  @AndrewChamb @awscloud It actually wasn’t able to do that, it could create new repos and PRs but not analyse and fix your own code. It would get downgraded. Sounds like you never used it.

• 
  Skunky (@skunky) reported 53 minutes ago

  @Marc269681 @awscloud These lying morons are covering for their mismanagement and poor decision making by blaming a toolset. It's like blaming photoshop for the fact that your are a terrible photographer.

• 
  참새 울음 소리는 칭어뤵뤵 (@20miracle17) reported 57 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.

• 
  Julley Thai (@julleybuilds) reported 1 hour 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