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

• 
  Marek Serafin (@stoprocent) reported 9 minutes ago

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

• 
  Jeff B. Vockrodt (@JeffBVockrodt) reported 9 minutes ago

  @AWSSupport You should send follow up emails alerting all your customers to this issue. I woke up to a $719 million billing estimate which although absurd conjures a potential nightmare of getting it worked out

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

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

• 
  Edward Donner (@edwarddonner) reported 14 minutes ago

  @BaconOverflow @awscloud I'm an experienced technologist. Yes a bug was likely. My fear was I'd made a terrible mistake or leaked credentials. AWS customers are on the hook for either. AWS has no hard caps. My initial alerts were high but not billions. For 10 mins I thought this just might be real.

• 
  Santhosh (@santhoshv) reported 14 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

• 
  bittermelon (@melon_thief) reported 16 minutes ago

  @AWSSupport Moving my domains and hosting to Cloudflare. There should have been a service bulletin on the billing page explaining the issue

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

• 
  Matt Teixeira (@matt_teeixeira) reported 17 minutes ago

  @priyansh_ptl18 @awscloud @AWSSupport Error I'm sure?

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 18 minutes ago

  Is something wrong with Opus again today? Yeah. Def not running my bug fixer until this is fixed. It’s struggling. I just did AWS + CLI update but I think it was struggling before that. Practically unusable right now. I write one file to list and run one of my projects with bash trace. It messed up the project menu. There’s that M word again. But it fixed it. Very, very slowly. Next I added a menu option to trace the log in a separate step that I can watch in a different window. It’s building the exact same project list with the same script. It messed up the project list AGAIN. I mean it literally just wrote the exact same thing in another file. So I tell it to make it work like the other file. It is crawling. One line every 10 seconds feels like. I told it just do what you did in the other file you just created. It’s been many rounds. It is inserting variables referencing things it doesn’t need like the memory files and config files from the other projects when I never told it to do that and it has not reason to do that. It only needs to write one line to trail the debug log. What the heck? Time to walk the dog and hope it is fixed when I get back. Using AWS Kiro CLI + Opus 4.8 An older version of Kiro CLI but nothing has changed there so no reason for it to not work as good as it did yesterday. Will be updating shortly but the problem is something else. Oh there it is. Opus 4.8 not available. @AnthropicAI @awscloud @kirodotdev

• 
  hellosowmya (@hellosowmya) reported 20 minutes ago

  @AWSSupport If my account is blocked for some reason then why I am allowed to login and purchased the reserved instance.please help on this. #aws #Awssupport #Ec2 @awscloud

• 
  Ing. Mario Varón M.Sc (@ma_varon_col) reported 20 minutes ago

  @AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...

• 
  J.D. Hollis (@consultingcto) reported 21 minutes ago

  @QuinnyPig @thinkx @awscloud lol. I guess that explains why we had a throughput problem at ProServe getting engagement contracts reviewed.

• 
  Jack Stone (@c0XhHxvylL) reported 24 minutes ago

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

• 
  AntDracula (@ant_dracula) reported 24 minutes ago

  @_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error

• 
  paige s. (@PaigeSully88) reported 27 minutes ago

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

• 
  dale (@daleverett) reported 28 minutes ago

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

• 
  Shaaaaaaaaan (@AryavartKSamrat) reported 31 minutes ago

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

• 
  riffy (@riffydays) reported 32 minutes ago

  Today, a rare break outside ended when a $90B bill hit my inbox and sent me rushing back I learned it was a bug from AWS Support on X—but finding out this way is a problem. If the bill came by email, why not the notice? Premium pricing. Anything-but-premium service @AWSSupport

• 
  Jayden L. (@Jwayy77) reported 34 minutes ago

  @awscloud Screw you aws. Not a joke, how many of us were pulled into the call to fix and understand the issue? How many of us init teardown scripts to stop all instances or remove the project? Clearly compensation is needed here. Look into it, else we’ll pack up and leave.

• 
  DeeDee Armstrong (@deedeeafton) reported 35 minutes ago

  @Gozieuk @awscloud You felt they were transparent? I got the anomaly detection email from AWS last night. Dashboard had an outrageous $$ number. Spun up devs to find out problem. And- then AWS posted a joke here on X, and still no email as a follow up to their first one. Doesn’t seem transparent

• 
  Matthew (@OneShotCaller) reported 35 minutes ago

  @CalebChamberla6 It’s an AWS billing error (see @awscloud)

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

• 
  Koray Yersel (@korayyersel) reported 47 minutes ago

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

• 
  Robert Culver (@senorculver) reported 48 minutes ago

  @awscloud Wow, that’s it, no explanation? No, and for your trouble, and extra work and panic, a free month of service or anything. Just our bad, see you next month?

• 
  That Other Hecate (@HecateKeys) reported 56 minutes ago

  @OwenGregorian 1) Forgets how DNS works. AWS goes down for days. 2) Forgets how arithmetic & metering works. Trillion-dollar bills for scant usage. @awscloud Regretting all those mass layoffs of your veteran engineers yet?

• 
  V0LYX (@0xV0LYX) reported 59 minutes ago

  @awscloud clear communication like this builds trust fast the fix matters but the transparency matters more

• 
  Erin (@erinEncoded) reported 59 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?

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 1 hour 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?

• 
  Armando J. Perez-Carreno (@perezcarreno) reported 1 hour ago

  @ngriffin_uk @awscloud The problem wasn’t only the billing page. Many people received billing usage alerts with tremendous spend. In our case, it was additionally frustrating because we couldn’t log in due to an MFA bug while we were about to board a ten hour flight. Some of us do care.

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