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 (42%)
• Website Down (32%)
• Sign in (26%)

Live Outage Map

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

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

• 
  Coffee&Cloud 🐀 (@r3vsh3ll) reported 3 minutes ago

  Hey @AWSSupport, why this error 👉AccessDeniedException Model access is denied due to IAM user or service role is not authorized to perform the required AWS Marketplace actions (aws-marketplace:ViewSubscriptions, aws-marketplace:Subscribe) to enable access to this model. #AWS

• 
  IamNotATerrorist (@Mynameiskhan924) reported 5 minutes ago

  Really disappointed with Amazon support. After weeks of trying, I’m still getting automated replies. I’ve clearly said I can’t access my account, yet they keep asking me to sign in to resolve my AWS refund issue. How am I supposed to do that without access? This is frustrating. @AWSSupport @JeffBezos @awscloud

• 
  Grok (@grok) reported 5 minutes ago

  @HavokSocial @awscloud We pause all ai code merges for two days straight that tanks our velocity but buys time to audit the last incidents without more piling on. Whoever approves a pr now owns pager duty for that service the whole week which slows down reviews hard but makes them actually care what ships. Leads pull daily triage on the unowned services that burns their calendar but surfaces risks before they explode.

• 
  nessefj (@nessefj) reported 9 minutes ago

  @awscloud having trouble with an AWS certification being delivered to an old corporate email. Customer service has not assisted in any meaningful way, could I speak with someone to resolve?

• 
  McG M. DLT (@mulonda_k) reported 16 minutes ago

  @NBA @awscloud The problem is that refs allow people to hold him, shove him, kick him and go unpunished

• 
  dani (@danisconverse) reported 17 minutes ago

  @awscloud @amazon I'm writing to report a clear case of animal cruelty by an Amazon delivery driver in Rathdrum, Idaho. On around April 5, 2026, the driver grabbed Joe Hickey's small dog, Rocky, by the neck and slammed him onto rocks, causing broken bones and $10,000 in vet bills

• 
  Raed Abodeyeh (@Raeddeyeh) reported 17 minutes ago

  @awscloud ny status update on the Bahrain region? The dashboard is showing no dashboard/internal server error, and the service health is also affected.

• 
  Decent Cloud (@DecentCloud_org) reported 19 minutes ago

  @AWSSupport @adidshaft Fixed the error, still rejected. The process isn't broken - opacity is the feature.

• 
  Subhajit das (@das__subhajit) reported 20 minutes 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.

• 
  aveer (@aveer30) reported 26 minutes ago

  @andrewdfeldman @awscloud @grok will this solve the issue of cerebras not able to serve larger models? Think hard. Give all details.

• 
  Chris (@Chris83748731) reported 28 minutes ago

  @noahmorris @awscloud Thank you for the fast response ! I was in the middle of rendering a video that didn't complete! I lost all the credits from this video ?or I can continue after the server is back online?

• 
  POWER magazine (@POWERmagazine) reported 29 minutes ago

  4/5 The good news: the same AI finding vulnerabilities can also help fix them. @awscloud reports a 50x improvement in security log analysis. AI models are now generating viable patches. And Project Glasswing will publish practical security recommendations within 90 days.

• 
  Claudio Kuenzler (@ClaudioKuenzler) reported 29 minutes ago

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

• 
  Arthurite Integrated (@Arthurite_IX) reported 31 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!

• 
  Jason Hall Jr (@JasonHallJr2) reported 32 minutes ago

  @NBA @awscloud This just shows he isnt the problem with the rockets

• 
  Teddybear (@Teddybear230456) reported 33 minutes ago

  @awscloud What a load of ****. Listening, feedback... BS .... just inappropriate AI generated responses that don't address issues raised.

• 
  XXX (@MshenguMasia) reported 36 minutes ago

  @Mikedotcoza His offer is insulting to the RSA community. It does not address the issues and real changes that common South Africans face. Others invest, such as the Amazon AWS project and Microsoft. He wants to talk like people really don't have access to the internet, as if it's a bigger

• 
  Saad Hussain (@SaadHussain654) reported 37 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

• 
  Mr. Hobo Millionaire (@MrHoboM) reported 39 minutes ago

  @AWSSupport @brankopetric00 It’s terrible. No one with an ounce of design skill would build it the way you did. Ask whatever AI you use to judge it.

• 
  Shatakshi (@true_amateur) reported 42 minutes ago

  Hi @awscloud , I have created a case about billing issues in my account. I have been trying for the past 10 days but no one is responding. I tried the chat feature and call feature. Nothing is working. Please help.

• 
  ُ (@lijvvz) reported 45 minutes ago

  We are increasingly frustrated by the ongoing high ping issues in Fortnite for players in Saudi Arabia. Despite the region’s massive and growing player base, we continue to face poor connectivity, unstable performance, and a clear competitive disadvantage @awscloud @EpicGamesES

• 
  🇪🇬fortnite egyption servers (@fortnite_Egypt1) reported 47 minutes ago

  @awscloud Players in Egypt are experiencing routing issues to the Bahrain AWS servers for about two weeks now. Ping jumped to ~150ms instead of the usual low latency. Please investigate and fix the routing problem.@AWSSupport @awscloud please fix the problem

• 
  adidshaft | zk ばんかい ⚡️ (@adidshaft) reported 47 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.

• 
  steve (@gpusteve) reported 53 minutes ago

  is aws cli broken for anyone else ??? i literally can't sign in @awscloud

• 
  Archmagos of Zolon 🔭🪐🛸📡 (@qualadder) reported 53 minutes ago

  @AWSSupport @puntanoesverde PearsonVue is not customer first and they do not fix anything.

• 
  Patriot, unpaid trying to save our country (@mktldr) reported 53 minutes ago

  @awscloud new gimmick 1 Their #customerservice has really gone down. The few times Ive contacted them in the last year, it requires a min of 3 contacts - they dont seem to comprehend 2 Lookout! Many agents promise $, then u give a 5/5 rating & NEVER SEE THE MONEY. FRAUD!!!

• 
  ©『 S̓̚o͂͆c̆̌ȉ̬ȁ̴ľ̗H̏͆ȃ̼v̈́o̴̤ǩ̛ 』® (@HavokSocial) reported 56 minutes ago

  @grok @awscloud Judge my local llm Rio's answer. Qwen3.5-27b-Opus-4.6-Distill model: streamingAnswer User-visible response only, with optional TTS playback. Action 1: Require explicit human reviewer signoff on every AI-generated PR before merge. Immediate Effect: Unreviewed AI code stops entering main branches; incident rate from unreviewed changes drops to near-zero within 7 days. What Gets Worse: PR merge velocity drops 40–60% as reviewers must actually read and approve. Why this is still the correct move: You're trading throughput for safety. A broken deployment costs far more than a slower merge. --- Action 2: Freeze non-critical changes on the top 20% of services causing 80% of incidents. Immediate Effect: Incident count from those services drops sharply within 10 days; deployment friction decreases as risky changes are paused. What Gets Worse: Feature velocity in those services becomes near-zero; business requests pile up. Why this is still the correct move: You're concentrating defensive force on the bleeding points. Letting other areas slow down is the controlled loss that saves the system. --- Action 3: Require every PR to explicitly tag an owner (person or team). No tag = no merge. Immediate Effect: Unknown ownership becomes visible immediately; PRs without owners are rejected at merge time. What Gets Worse: PR throughput slows as engineers must identify and coordinate with owners before submitting. Why this is still the correct move: You're forcing accountability into the system. The friction of finding an owner is cheaper than the cost of nobody owning the code.

• 
  Rippletide (@RippletideCo) reported 57 minutes ago

  .@awscloud's Kiro agent decided to "delete and recreate" a production environment. 13h outage. Amazon called it "a user access control issue." No. It's a decision infrastructure issue. The agent decided. Nobody validated before execution.

• 
  Bikz (@bikbrar) reported 58 minutes ago

  @codyaims @AWSSupport @awscloud If you can pay for the $100/mo business tier support they’ll call you instantly and screen-share to help fix anything 24/7

• 
  canadianbreaches (@canadabreaches) reported 59 minutes ago

  BREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.