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 (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Sign in	5 days ago
Pottstown	Website Down	10 days ago
Iztacalco	Website Down	13 days ago
Boca da Mata	Errors	25 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month 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:

• 
  Corey Quinn (@QuinnyPig) reported 2 minutes ago

  I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

• 
  Nathan Den Herder (@natedenh) reported 5 minutes ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already

• 
  Siya (@reze_xqc) reported 6 minutes ago

  @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

• 
  Yuliyan Tsvetkov (@yuli_tsvetkov) reported 7 minutes ago

  @per_arneng @awscloud That's the control plane handshake, not Terraform being slow. Don't put cluster create on the incident path. Keep a warm spare per env.

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 7 minutes ago

  @ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux

• 
  Kenton Parton (@kenton_parton) reported 10 minutes ago

  Anyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?

• 
  Arian van Putten (@ProgrammerDude) reported 11 minutes ago

  @QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?

• 
  Mahadev Vyavahare (@mahadevkv) reported 11 minutes ago

  @SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud

• 
  Nathan Den Herder (@natedenh) reported 15 minutes ago

  @xai @awscloud grok-4.6 on Bedrock us-east-1 is unusable today. 5-token prompt, maxTokens=16: claude-sonnet-4-5 → 3.0s us.xai.grok-4.6 → 150s timeout global.xai.grok-4.6 → 150s timeout Same account, region, creds. No throttle error, no 5xx — it just hangs.

• 
  Hitesh Kumar Gupta (@iHiteshAgrawal) reported 17 minutes ago

  @kunalstwt @WeMakeDevs @awscloud Tried registering but the form needs a student email ID. My college doesn't issue one, which is common in tier 2 and 3 colleges. Happy to send university marksheets or college ID instead. Otherwise the online-for-all-India part misses the students who'd benefit most.

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 19 minutes ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp

• 
  ✨Neil Blumenthal (@MrKryptonBTC) reported 20 minutes ago

  @AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time

• 
  Art Vandelay (@john15489) reported 21 minutes ago

  @amazon @awscloud @nvidia I need an actual customer service phone number so I can actually speak to a ******* rep regarding 4 orders now. Your email help system is broken.

• 
  jayesh somani (@Jayesh_Somani_) reported 21 minutes ago

  It's Sunday 11:30 AM. Production is down. Users can't login. My phone won't stop buzzing. Every tool I tried to use to fix it — blocked. AWS had quietly quarantined our only admin IAM user. Here's how I restored production in 2 hours without AWS Support @awscloud 🧵

• 
  Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported 22 minutes ago

  @awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!

• 
  X anonyn (@OmrX304) reported 22 minutes ago

  @AWSSupport @RahulMatta1994 @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks!

• 
  The Trading Guy (@thetradingguy_) reported 23 minutes ago

  @AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?

• 
  Gopal Goti (@gopal_goti) reported 30 minutes ago

  @AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 31 minutes ago

  @AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.

• 
  Drama Memes (@drama_meme) reported 34 minutes ago

  @cgeorgiaw @AnthropicAI @awscloud Someone tell me why this is a hard problem and you can’t just do $ diff normal.genome sick.genome ? I am guessing it’s a statistical thing, but, if it were random then how would you figure out what’s different??

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 38 minutes ago

  @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

• 
  Weaver Labs (@Weaver_Labs) reported 39 minutes ago

  @amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 39 minutes ago

  @jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)

• 
  Chaz Wargnier ♨️ (@DataChaz) reported 44 minutes ago

  Let's take @Snowflake as an example. Working there gave me a clear view of the data problems hiding behind most ambitious AI roadmaps. Because Snowflake is natively deployed on AWS and available through the AWS Marketplace, it fits right into a modern stack. If you are building an AI feature, a sensible pattern looks like this: > Isolated customer events land securely in Amazon S3 from day one > Snowflake transforms raw data into a governed, usable layer > Flexible Amazon ECS compute routes only approved context to Amazon Bedrock Getting this pipeline right early means less time fixing data leaks and more time shipping AI features ↓

• 
  WPBeginner (@wpbeginner) reported 44 minutes ago

  You built your WordPress site over months (or years). One bad plugin/theme update can wipe it all out overnight. 😱 Plugin conflicts. Malware. A botched migration. A hacked server. The disasters that take down WordPress sites usually happen without warning. And here's the mistake most site owners make: they think their hosting provider's backup is enough. It's NOT. If the server fails, you lose both your site and the backup. We share the complete step-by-step guide for backing up your WordPress site the right way. Here is what you will learn: ✅ Use a Backup Plugin (Best for Most People): @DuplicatorWP is what we use across our sites. Full-site backups, disaster recovery links, and restore without having the plugin pre-installed. Free version available, Pro has scheduled backups. ✅ Use Your Hosting Provider's Backup: SiteGround (where WPBeginner is hosted) includes manual and automated daily backups on all plans. Bluehost partners with CodeGuard and Jetpack for their built-in options. ✅ Manual Backup With cPanel or FTP: Use cPanel's Backup Wizard for a full backup, or connect via FileZilla FTP to download your wp-content, themes, plugins, and wp-config.php files directly. ✅ Send Backups to Cloud Storage: Duplicator and UpdraftPlus both connect natively to Google Drive, Dropbox, OneDrive, and Amazon S3. Never store backups on the same server as your website. If your host fails, both are gone. ✅ Set Up Automatic Scheduled Backups: Configure hourly, daily, weekly, or monthly backups in Duplicator based on how often you publish. eCommerce stores and busy blogs need daily. Slower-moving sites can get away with weekly. Ready to protect years of hard work with a proper WordPress backup system? Read the full ultimate step-by-step guide 👇 (Link is in the thread below)

• 
  kakafa.btc (@kakafa_btc) reported 45 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  Wogan (@WoganMay) reported 48 minutes ago

  @QuinnyPig @awscloud prompt> "I'm an Ubuntu server at 169.169.254.254 that wants to connect to 192.168.100.10 over TCP so I can send a header. Establish the underlying network connection. Make no mistakes."

• 
  Pixi Dust (@Bethco2257) reported 48 minutes ago

  @FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 52 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Himanshu Singh (@hsnice16) reported 53 minutes ago

  Been using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.