Elevated API latency
API performance has remained stable following mitigation. This incident has been resolved.
The latest update from Clerk.
State
Resolved
Started
62 d ago
2026-08-31 13:55 UTC
Lasted
1 h 45 min
until 2026-08-31 15:40 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
23 min 22%
Identified
1 h 5 min 62%
Monitoring
18 min 17%
Updates
Times in UTCAs posted by Clerk
API performance has remained stable following mitigation. This incident has been resolved.
Mitigation has been applied and API performance has stabilized. We've deployed additional safeguards and are monitoring to confirm continued stability.
We identified elevated traffic affecting the Backend API and user-related requests, causing increased latency and intermittent failures. We've applied mitigation and are monitoring its effect. We'll provide another update once we confirm service stability.
We're investigating elevated latency and intermittent timeouts affecting Clerk API requests. Some customers may see slow responses when loading user and organization data. Our team is looking into it and will post another update once we have more information.
Clerk in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
31
Median duration
3 h 26 min
This incident
49% shorter than the median
Other Clerk incidents
All incidentsClerk·SMS Delivery Issues
The SMS delivery issue is resolved. Delivery and verification completion rates have returned to normal following our upstream provider’s switch to an alternate route.
Clerk·Issues with Documentation "Ask AI"
The Ask AI functionality in Clerk docs has been restored.
Clerk·Dashboard increased latency
The incident is now resolved
Clerk·Development instances only - Apple rejecting emails
Despite extensive efforts to reach out to Apple about this issue we still do not have a resolution from them. As this incident has been ongoing for over a month, we have decided to move towards displaying a warning message on sign in from development instance when apple emails are used to sign in and taking down this incident notification. We apologize for the inconvenience and genuinely hope that we hear back from Apple soon on this matter.
Clerk·Delays in webhook delivery
All systems are functional
Follow Clerk
Your coding agent knows when Clerk is down, and tells you when a failure is theirs, not yours. You can also get Clerk incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "clerk" and tell me if Clerk has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=clerk/feed subscribe https://outages.cc/feed.xml?providers=clerkFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane