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 (17%)
• Errors (17%)

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

• 
  Shaaaaaaaaan (@AryavartKSamrat) reported 6 minutes ago

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

• 
  Ing. Mario Varón M.Sc (@ma_varon_col) reported 14 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...

• 
  Negi (@negihere) reported 18 minutes ago

  @sorower01 @awscloud I did not login into account yet any uses it’s showing ??

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

• 
  Jayden L. (@Jwayy77) reported 30 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.

• 
  D (@D8118199174282) reported 32 minutes ago

  @awscloud No, you still haven’t compensated users for the cost bug error

• 
  Ashutosh Dubey (@_virusbug_) reported 35 minutes ago

  @AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue. @AWSSupport

• 
  IDrabs (@drabs_i) reported 38 minutes ago

  @PlayStation @awscloud Wtf you playing at fix the outage.

• 
  𝘋𝘳. 𝙈𝙞𝙘𝙝𝙖𝙚𝙡 𝙅. 𝙋𝙚𝙩͛𝙚𝙧𝙨𝙤𝙣 (@WeatherArchive) reported 40 minutes ago

  Somehow, GOES19 going down wasn’t the craziest thing to happen this week. Happy bankruptcy day to those who celebrate (I.e., have an @awscloud account)

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

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

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

• 
  Nil (@slowalgorithm) reported 42 minutes ago

  @awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 42 minutes ago

  @yellow_fellowz @awscloud @emm3122 AWS replied to me saying they’re aware of this issue

• 
  J Bret Edwards (@jbecompslns) reported 43 minutes ago

  did @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.

• 
  Matt Teixeira (@matt_teeixeira) reported 44 minutes ago

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

• 
  Master of Controversy (@THe0GAmer) reported 44 minutes ago

  @Pirat_Nation Amazon aws outage knocked psn offline for 8 hours while sony pushes an all digital future fans could not launch their purchased games

• 
  Ryan Varghese Mathew (@RyanVarghese14) reported 46 minutes ago

  Hi @awscloud @AWS I am currently facing issues from regarding certain payments. And despite incessantly reaching out on the support team and the email, I have been charged and there has been no formal support extended. I know you guys can do better than this.

• 
  YorkshireSarah (@SarahSWFC1867) reported 46 minutes ago

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

• 
  Vaibhav Khatri (@vaibhavkhatrii) reported 47 minutes ago

  @AWSSupport Believe me when I saw this, I had to check my BP. No issue is more than someone’s life.

• 
  Jaden Fix (@jadenfixxx) reported 51 minutes ago

  Anyone at @googlecloud or @awscloud (or a neocloud) wanting to slide into my DMs and help me rip some free credits? Possibly leading to larger contracts down the road .. I just tried signing up for an @Azure free trial, and the experience felt like what I imagine the elders went through with dial-up internet. Solutions Architects or Account Managers HMU

• 
  Abhi Bavishi (@abhibavishi) reported 54 minutes ago

  Seems like a major glitch with @awscloud

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

• 
  Drate Berry (@drateberry) reported 57 minutes ago

  Is anyone else experiencing issues with the @awscloud Billing system? I’m trying to add a new card and both the physical and virtual versions are throwing a verification issue. Bank is saying they don’t see anything on their end. Waiting to hear back from AWS Support.

• 
  Steven Coburn (@pcgamer11) reported 57 minutes ago

  @PlayStation We can't play the open beta rn because PSN IS DOWN. Yes, it uses/runs on @awscloud but you could at least ACKNOWLEDGE the issue!!!

• 
  AntDracula (@ant_dracula) reported 59 minutes ago

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

• 
  Mr. Honkitude (@Mr_Honkitude) reported 59 minutes ago

  @St0ner1995 @AWSSupport When you owe someone $10k, you have a serious problem. When you owe someone $110 billion, they are the one with a serious problem.

• 
  Jyothish Nalinakshan (@GunnerJyo) reported 1 hour ago

  Hi @AWSSupport , I need assistance with an AWS Builder ID account issue that affects my AWS Certification and learning history. I have already opened two support cases: Case #178395122100863 (MFA Support Form) Case #178395287500121 (Billing & Account Support Form)

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

• 
  PositiveVibes (@KPTheFighter) reported 1 hour ago

  @AWSSupport @AWS @awscloud I still did not receive any email communication which I was expecting as soon as you guys noticed the issue. Today I almost lost my life due to panic. My hands were shaking as I was told. I still can’t believe I went through this. First email - insane actual bill about Dashboard shows the same amount After panic attack, I see a note on your support page, but what would one go to your support page ? Shouldn’t it be on your billing console page ? Again, my issue is not about your mistake, it’s about how you handled the situation. And you didn’t do anything!! Not even one email to the users!! Sad and shocked at the same time!! I can’t forget what I went through today morning. 😞

• 
  deibeat (@deibeat_13) reported 1 hour ago

  @AWSSupport I did the same exactly, and really panicked when I saw that, thought someone got access or something. Tried to contact billing support, removed s3 bucket, turned off a personal website using it, asked Claude for guidance until I finally found it was a global issue…