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.

• Errors (41%)
• Website Down (32%)
• Sign in (27%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
West Babylon	Errors	3 days ago
Massy	Errors	4 days ago
Benito Juarez	Errors	8 days ago
Paris 01 Louvre	Website Down	12 days ago
Neuemühle	Errors	12 days ago
Rouen	Website Down	12 days 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:

• 
  Neil harrison (@Neilharrison89) reported 8 minutes ago

  @RuthBuscombe @awscloud Stop calling it macarena wing it Spanish to start and has nothing to do with flipping upside down, let's stop being silly and call it what it is a flip wing, just stop with the macarena you all sound like you have a low iq calling it macarena wing

• 
  Forward Future (@ForwardFuture) reported 10 minutes ago

  “Will Amazon ever sell its custom chips outside of AWS?” Matt Garman, CEO @awscloud, says: “Never say never. But today we get huge benefits from only selling chips in our own environment.” “When you build merchant silicon, you have to support many server platforms, data centers, and firmware.” “We only have to build for one: AWS. That simplifies everything.”

• 
  Super Stiff Yogi (@SuperStiffYogi) reported 10 minutes ago

  @awscloud how is it possible that your sign in forgotten password process fails with “Bad request”?! And your email case support is so bad it makes no attempt to assist?

• 
  N (@namzylll) reported 11 minutes ago

  Ignoring the Middle East when it comes to servers is a huge oversight. ALOT of players are stuck with 130+ ping. FIX THEM!!!! @FortniteStatus @awscloud @FortniteME #fortniteriyadh

• 
  Farooq Rana (@RanaFarooqAslam) reported 12 minutes ago

  @awscloud me-central-1 is down from last 7 days, no updates, still cannot get services or data, no timeline

• 
  Decent Cloud (@DecentCloud_org) reported 14 minutes ago

  @Mn9or_ @AWSSupport No support subscription means you wait for someone else's ticket to fix your outage

• 
  Ted (@Zuffnuff) reported 18 minutes ago

  @F1 @awscloud Keep trying to spin it but these cars have a physics problem. Fake race cars.

• 
  Mike Dupont (@introsp3ctor) reported 22 minutes ago

  @AWSSupport the billing ticket is open for days, and the discord and the github and absolutly no response from aws or kiro. Its seems like another release on a friday issue, so i will wait a bit happy holidays. my guess is they ran out of money and had to pause a bunch of accounts in loss.

• 
  Tim Reynolds (@__timreynolds) reported 23 minutes ago

  @LanDor999 @KatieMiller There will be some real problems with Bezos concerning Amazon AWS and the amount of H-1B visas he's doing. Between the massive layoffs, robotics, and warehouses, $200 billion spent, and counting on AI. another startup is going to do it right from the ground up

• 
  Ralf Rolfen (@Hagebuttentee12) reported 23 minutes ago

  @awscloud Problem: RDS Snapshot re-creation and Cloudformation / CDK are a maintenance nightmare. FR 1. Change SnapshotIdentifier to not be a replacement property when changed to empty FR 2. CDK: Merge DatabaseCluster and DatabaseClusterFromSnapshot into a single class.

• 
  adidshaft | zk ばんかい ⚡️ (@adidshaft) reported 24 minutes ago

  @AWSSupport there’s nothing annoying i’m just kidding. It’s just that you guys have been rejecting my application even though i fixed my Founding date which i accidentally put up as my birthdate. You have been rejecting with same issue even tho i fixed it.

• 
  Jenifer Rajendren (@enravishjeni411) reported 26 minutes ago

  Is AWS service gone for a toss? Login page is loading for about 10 minutes @AWSCloudIndia , @awscloud

• 
  Claudio Kuenzler (@ClaudioKuenzler) reported 27 minutes ago

  Whoa. Did @awscloud Frankfurt just go down for 2 mins ~5min ago?

• 
  distribute.ai (@distributeai) reported 27 minutes ago

  aws ( @awscloud ) is officially supporting x402 payments so your ai agents can autonomously buy their own api access using usdc. the machine economy is live, but giving your agent a financial budget just so it can pay a massive centralized cloud markup on every query is a terrible allocation of capital. route your autonomous workflows through the distribute network. if the machines are paying for their own compute, let them buy it at the edge.

• 
  Bryan (@0xp4ck3t) reported 33 minutes ago

  @AWSSupport We have business + and we should be able to get a response from AWS within 30 minutes for critical issues. It's been hours, our **** DB is down. We need someone to have a look on it. Case ID 177566080000785

• 
  Anmol Thakur (@ImAnmo07) reported 38 minutes ago

  Hi @AWSCloudIndia @awscloud, I'm trying to set up a Bedrock Knowledge Base using Amazon OpenSearch Serverless, but I'm getting the error: “Failed to create the Amazon OpenSearch Serverless collection. The AWS Access Key Id needs a subscription for the service.”

• 
  Zaid (@zqureshi_) reported 40 minutes ago

  @Tahalazy @AWSSupport can confirm, facing same issues @AWSSupport

• 
  Saad Hussain (@SaadHussain654) reported 40 minutes ago

  @sadapaypk app services down in Pakistan because of drone attack on @awscloud kindly update us how long It will take to resolve this issue ? We are suffering from 1,2 days

• 
  Decent Cloud (@DecentCloud_org) reported 42 minutes ago

  @AWSSupport @CPGgrowthstudio Production down 5 days. The response commits to nothing. Next customer with this issue finds the same boilerplate.

• 
  Basil K (@gotobasil) reported 44 minutes ago

  @awscloud : UAE data center DOWN for 2 DAYS! No response to tickets, no assignments, zero communication. We've exhausted every channel to reach you. How can businesses trust AWS when we're STUCK without app access? This kills our operations! #AWSOutage #UAE #CloudFail

• 
  Arthurite Integrated (@Arthurite_IX) reported 46 minutes ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  Manas Vardhan (@manas__vardhan) reported 47 minutes ago

  @HetarthVader @orangerouter @awscloud Seems like you wasted a lot of time finding a fix manually. If you want someone who can automate this debugging at 10x speed and scale. Let me know. I'm a researcher at USC, prev at JPmorgan. I automate stuff for fun.

• 
  Decent Cloud (@DecentCloud_org) reported 48 minutes ago

  @AWSSupport @theodorebeers GitHub feedback. No case ID. No SLA. Problem solved - for AWS.

• 
  Ignacio G.R. Gavilán (@igrgavilan) reported 48 minutes ago

  @awscloud_es @AWS @awscloud I need to talk urgently with you. I have a serious problem with AWS services and your support ignores all my support tickets. I prefer an in-person contact, in spanish if possible.

• 
  Jordan Golson (@jlgolson) reported 48 minutes ago

  @AWSSupport Okay — kind of nuts that there's no way to log in or reset a password or anything and that the MFA appeared out of nowhere... also that you can have the same login for AWS Builder AND AWS Console and there's no great explanation for why they're different.

• 
  Roberto Shenanigans (@Rob_Shenanigans) reported 53 minutes ago

  @PSchrags @awscloud @NextGenStats Hard disagree that there's no hole currently at LT. Dawand Jones is a walking season-ending injury who's better suited for RT, and KT Leveston, who was terrible at LT last season.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 54 minutes ago

  @HashiCorp @awscloud Unmanaged secrets in S3 is a real problem especially in fintech where you have long running services that accumulate config files, export artifacts, and database dumps over years. The hard part is not the scanning, it is what you do with the findings. Rotation pipelines and downstream dependency mapping are where most teams get stuck after discovery.

• 
  Ser-Jet💜👑(🧩) (@Ser_Jettt) reported 58 minutes ago

  @JothamNtekim1 @awscloud Interesting approach to the problem. Are you currently exploring any builder challenges or just shipping independently?

• 
  Super Stiff Yogi (@SuperStiffYogi) reported 1 hour ago

  @AWSSupport The next steps are just the same documentation links which do not address my specific issue. If you read the case carefully you would see that. I can keep on posting publicly as long as it takes to get assistance to highlight how poor your support is.

• 
  Subhajit das (@das__subhajit) reported 1 hour ago

  In 2017, Amazon S3 went down and took a massive chunk of the internet with it. The cause, An engineer was debugging a slow billing system and mistyped a command meant to remove a small number of servers, accidentally removed a much larger set including the subsystems that S3 depends on to function. Slack, Trello, GitHub, Quora, Medium, all hit. Even Amazon's own status page went down because it was hosted on S3. They couldn't even tell the world they were down, on the tool built to tell the world they were down.