outages.live
Live
ClerkIncident · 2026-10-21 23:50 UTC

Issues with Documentation "Ask AI"

ResolvedOfficial update

The Ask AI functionality in Clerk docs has been restored.

The latest update from Clerk.

State

Resolved

Started

10 d ago

2026-10-21 23:50 UTC

Lasted

45 h 47 min

until 2026-10-23 21:37 UTC

Worst impact

Degraded

Timeline

2 updates
Oct 21Oct 22Oct 22Oct 23Oct 23
DegradedUpdate postedDates in UTC

Identified

45 h 47 min 100%

Updates

Times in UTC

As posted by Clerk

Resolved2026-10-23 21:37 UTC

The Ask AI functionality in Clerk docs has been restored.

Identified2026-10-21 23:50 UTC

We are investigating an issue with the Ask AI functionality in the Clerk Docs.

Clerk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

31

Median duration

3 h 26 min

This incident

13× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 days
median 3 h 26 min
90 days agoToday

Other Clerk incidents

All incidents

Clerk·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.

Resolvedresolved 3 d ago

Clerk·Dashboard increased latency

The incident is now resolved

Resolvedresolved 30 d ago

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.

Resolvedresolved 13 d ago

Clerk·Delays in webhook delivery

All systems are functional

Resolvedresolved 46 d ago

Clerk·Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients

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

Resolvedresolved 58 d ago

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.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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane