outages.live
Live

Clerk

Clerk is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

30

Median duration

3 h 26 min

Longest incident

21 days

Components

16
Authentication & User Operational
90 days agoNo incidentsToday
Machine authentication Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Hosted UIs (Account Portal) Operational
90 days agoNo incidentsToday
Session management Operational
90 days agoNo incidentsToday
Multi-tenant authentication Operational
90 days agoNo incidentsToday
SCIM Operational
90 days agoNo incidentsToday
Billing Operational
90 days agoNo incidentsToday
Email delivery Operational
90 days agoNo incidentsToday
SMS delivery Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Dashboard analytics Operational
90 days agoNo incidentsToday
Dashboard search Operational
90 days agoNo incidentsToday
Application "Go live" Operational
90 days agoNo incidentsToday
Platform API Operational
90 days agoNo incidentsToday
Ask AI Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration36 min17:40 to 18:16SMS Delivery IssuesPartial outage

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.

Oct 21, 2026

Duration45 h 47 min23:50 to 21:37Issues with Documentation "Ask AI"Degraded

The Ask AI functionality in Clerk docs has been restored.

Oct 1, 2026

Duration14 h 19 min16:10 to 06:29Dashboard increased latencyDegraded

The incident is now resolved

Sep 28, 2026

Duration21 days15:23 to 17:39Development instances only - Apple rejecting emailsDegraded

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.

Sep 16, 2026

Duration1 h 8 min12:31 to 13:39Delays in webhook deliveryDegraded

All systems are functional

Sep 4, 2026

Duration4 h 34 min10:06 to 14:40Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipientsDegraded

Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.

Sep 1, 2026

Duration3 h 26 min15:48 to 19:13GCP incident in us-central1-bDegraded

Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.

Aug 31, 2026

Duration1 h 45 min13:55 to 15:40Elevated API latencyDegraded

API performance has remained stable following mitigation. This incident has been resolved.

Aug 4, 2026

Duration37 min23:03 to 23:40Increased API latency and errorsDegraded

We've resolved the issue with our upstream provider.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=clerk
Slack
/feed subscribe https://outages.live/feed.xml?providers=clerk

Go from tracking outages to fixing production issues with Polylane.

Try Polylane