惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
B
Blog
S
SegmentFault 最新的问题
Vercel News
Vercel News
博客园 - 聂微东
宝玉的分享
宝玉的分享
C
Check Point Blog
有赞技术团队
有赞技术团队
IT之家
IT之家
V
V2EX
爱范儿
爱范儿
GbyAI
GbyAI
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Azure Blog
Microsoft Azure Blog
P
Proofpoint News Feed
博客园 - 司徒正美
博客园_首页
Last Week in AI
Last Week in AI
博客园 - 叶小钗
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
F
Fortinet All Blogs
腾讯CDC
J
Java Code Geeks

Clerk Blog

Going to production with Clerk Deploy Clerk Init: The fastest way to start a new project Introducing Clerk CLI Middleware-based route protection bypass Postmortem: Clerk System Outage (March 10, 2026) Clerk for the AI era Add API Key support to your SaaS in minutes Postmortem: Clerk System Outage (February 19, 2026) Using Clerk in a React Native app Postmortem: DNS Provider Outage (February 10, 2026) How do I implement passkeys in Next.js? Clerk ranked #4 fastest-growing software vendor on Ramp’s December 2025 list How do I handle JWT verification in Next.js? Committing to Agent Identity: Clerk raises $50m Series C from Menlo and Anthropic’s Anthology Fund What is the best way to handle authentication in Next.js App Router? Postmortem: Database Incident (September 14–18, 2025) How do I add authentication to a Next.js app? Introducing Free Trials in Clerk Billing Introducing Mosaic: Bring Your Brand to Every Authentication Flow Multi-tenant authentication: What you need to know (and how Clerk helps) What are the risks and challenges of multi-tenancy? Resilience in Practice: Regional Failover at Clerk Build a Cross-Platform B2B App with Clerk, Expo, and Supabase Highlights from the MiduDev/Clerk Hackathon Add multi-tenancy to an app built with Clerk, Lovable, and Supabase How to build an AI coding rules app with Clerk, Lovable, and Supabase How to Build Multi-Tenant Authentication with Clerk Choosing the right SaaS architecture: Multi-Tenant vs. Single-Tenant Postmortem: June 26, 2025 service outage How to Design a Multi-Tenant SaaS Architecture
Postmortem: August 28, 2025 - elevated API latency and er...
Alex Ntousias, Agis Anastasopoulos · 2025-08-28 · via Clerk Blog

Category
Company

Published

On August 28, 2025, a credential stuffing attack caused elevated API latency and errors. This postmortem details the impact, root cause, and remediations.

On August 28, two short periods of a distributed credential stuffing attack to our authentication endpoints of a specific tenant, led to elevated latency across the Frontend and Backend APIs and elevated errors in the Backend API.

Services remained partially available while we mitigated load and stabilized the underlying infrastructure. Importantly, our mitigation controls kept session token issuance operating normally throughout the incident.

  • Impact window #1: 14:53–15:15 UTC (≈22 minutes)
  • Impact window #2: 17:04–17:16 UTC (≈12 minutes)

Timeline (UTC)

  • 14:53 — Alert triggered for high CPU utilization in the storage layer; elevated API latency observed.
  • 15:00 — Incident declared; mitigation initiated.
  • 15:15 — Metrics returned to baseline.
  • 17:04 — Second spike in CPU and API latency detected.
  • 17:16 — Metrics returned to baseline.

Root Cause Analysis

Investigation points to several compounding contributors in the authentication and data-write path:

  1. Automated traffic targeting authentication flows generated an unusually high volume of sign-in and sign-up attempts.
  2. Write-intensive activity from those attempts increased contention on hot authentication-related tables.
  3. A recently introduced CDC consumer (used for near real-time consumption of auth events) lagged under burst conditions, amplifying contention within a segment of the storage tier.

Observed error rates during the incident windows: 2.52% of Backend API requests and 0.14% of Frontend API requests returned errors.

There was no data loss or corruption. The impact was limited to increased latency and errors.

Remediations

  • We disabled the lagging change-stream processor pending adjustments.
  • We are strengthening adaptive protections at the edge and auth layer (rate limiting, anomaly detection, and upstream filtering).
  • We are performing schema and query-path improvements on authentication workloads to reduce contention under spikes.
  • We will be further strengthening per-customer isolation to contain issues to the originating application and minimize blast radius.