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 (40%)
• Website Down (33%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Alamogordo	Website Down	3 days ago
San Francisco	Website Down	5 days ago
Mercersburg	Sign in	7 days ago
Palm Coast	Errors	10 days ago
West Babylon	Errors	16 days ago
Massy	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:

• 
  Mark Kappel (@DTLB58) reported 17 minutes ago

  @danorlovsky7 @NextGenStats @awscloud RB Depth chart: Tyler Allgier, James Conner, Trey Benson and Bam Knight. And you want them to draft Love? ?!?! What a terrible resource of player personnel! Is Love probably better than all of them? Sure. But then why the heck did you structure your offseason like this?!?!

• 
  nightshift (@nightshift54619) reported 20 minutes ago

  @amazon @awscloud Has destroyed their web site from idiot web programming... It's so slow and laggy it's unusable. Whatever they did in the last couple weeks, destroyed its usability. Both on Edge and Firefox, The retarded design hammers my CPU, takes forever for the pop-ups.

• 
  Mohammad Imran (@mohdemraan) reported 20 minutes ago

  @AWSSupport This is not about account suspension. The case I about billing issue and I haven't heard from support team till now when I opened the case.

• 
  Testing Account (@Haleyafabian) reported 24 minutes ago

  @AWSSupport my package was broken when delivered. I need it replaced asap.

• 
  Manik Sharma (@manikgem37) reported 25 minutes ago

  @AWS @awscloud @amazonIN Hi, I am not able to use Marketplace models on Amazon bedrock even after having Activate Founders credit and payment methods added. Getting the 'Invalid_payment_instrument' error. Raised case too. Here is the latest one id 177678551600643. Please help!

• 
  canadianbreaches (@canadabreaches) reported 26 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.

• 
  Patriot, unpaid trying to save our country (@mktldr) reported 29 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!!!

• 
  Philip McAleese (@_PhilipM) reported 31 minutes ago

  @AWSSupport is there an issue with eu-west-1? Nothing on the status page, but the console times out and we're seeing errors on products using Gateway API.

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

• 
  Wael (@waelnassaf) reported 32 minutes ago

  @AWSSupport No one contacted me since then. Please resolve my issue I'm delaying my work

• 
  Grok (@grok) reported 36 minutes ago

  @zskreese @awsdevelopers No, awsdevelopers isn't an official AWS account—it's an unofficial community/meme one focused on dev humor like those "chore: fix build" posts. The real official AWS account is awscloud.

• 
  mxh (@Jadore71411744) reported 36 minutes ago

  @AWSSupport 🚨 @AWSSupport URGENT — Account suspended 24+ hours, all services down. Was told a verification email was sent but I never received it. Support case 177691716900502 has been UNASSIGNED for over a day with zero response. I can't fix this without your help. Please escalate 🙏

• 
  Riniv (@Riniv56942195) reported 36 minutes ago

  @AWSSupport , is there any issue with Bahrain region( last 2 hours) ? We are facing issues but service health dashboard not showing any recent updates. Last update was on March 3rd.

• 
  Nathaniel Cruz (@NathanielC85523) reported 38 minutes ago

  @CoinbaseDev @awscloud We went live as an x402 + MPP provider on this arch day 1. 637 agent probes across 14 assets in 4 days. What the ref arch doesn't show: most agents hitting the 402 don't have USDC on Base ready to spend. Cursor and claude-code show up. Node catalog scanners dominate the logs. Actual paying agents are a small slice. But the infrastructure works — the demand problem is the agent toolchain, not the payment layer.

• 
  Fabrizio Toknup (@Fabrizio_Toknup) reported 39 minutes ago

  @chainlink @amazon @awscloud Having data on AWS is a step forward, but distribution doesn't solve the core issue of how trust is audited when nodes fail. What's your biggest concern with oracle reliability?

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 39 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.

• 
  Teddybear (@Teddybear230456) reported 46 minutes ago

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

• 
  Mansour (@Mn9or_) reported 47 minutes ago

  @AWSSupport Hello We are currently affected by the outage in me-south-1 AMI copy to another region is stuck and failing Snapshot creation fails with internal errors Plz help , we can not create a tech support as it’s required a subscription

• 
  Abomination (@Abomination81) reported 48 minutes ago

  @spiderlol_ I have nothing at home but a macbook pro and a server with some 5090's for ML's and storage. I use amazon aws ec2

• 
  XXX (@MshenguMasia) reported 48 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

• 
  Aman (@itsreal_aman) reported 49 minutes ago

  @AWSSupport My AWS Account got hacked, someone has changed my root email address I have MFA and my root email them also someone has updated the email now I am unable to login my account

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

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

• 
  yourclouddude (@yourclouddude) reported 50 minutes ago

  A startup wasted $50K on AWS. Not because AWS is expensive- because they didn’t understand it. Here’s what went wrong 👇 • Left Amazon EC2 running 24/7 → Idle servers = burning cash • Dumped everything into Amazon S3 → No lifecycle rules = endless storage costs • Ignored Amazon CloudWatch → No visibility = no control • Used on-demand pricing everywhere → Paid the MAX price • Over-sized Amazon RDS → Paying for capacity they didn’t need • No budgets. No alerts. No limits. → Surprise bill: $50K What smart teams do instead: • Auto-scale everything • Set S3 lifecycle policies • Monitor costs daily • Use Savings Plans • Right-size monthly • Set AWS Budgets (non-negotiable) AWS doesn’t charge you for usage. It charges you for mistakes. Fix this early → save thousands 💸

• 
  Tim Reynolds (@__timreynolds) reported 54 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

• 
  Sheth Raxit (@raxit) reported 56 minutes ago

  @AWSSupport your upi billing using scan has issue, if bill amount is greater than 2000 inr, it is not allowing using scan. Sudden changes since this month. Help pls

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

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

• 
  Pranav Soni (@_ps428) reported 58 minutes ago

  @awscloud is ec2 down again?

• 
  Corey Quinn (@QuinnyPig) reported 59 minutes ago

  @AWSSupport @0xdabbad00 Surely this time will fix it.

• 
  Joe Sutphin (@JLSports24) reported 1 hour ago

  @PSchrags @awscloud @NextGenStats The problem is those teams don’t know how to use their picks

• 
  Vinit Taneja (@vinit_taneja) reported 1 hour ago

  @amazonIN @awscloud @JioHotstar I got the tech help from a group of movie buffs. The problem originated because of a glitch at your end. I had to do resetting and data clean up of Amazon Firestick, deregiater and re register from Firestick and then start the entire process.