Issues with Documentation "Ask AI"
identifiedWe are investigating an issue with the Ask AI functionality in the Clerk Docs.
Clerk is partly degraded. Clerk provides hosted authentication and user management.
Worked out from the incidents Clerk reported, so it is an estimate and not a measurement.
Last incident: “Issues with Documentation "Ask AI"”, today.
We are investigating an issue with the Ask AI functionality in the Clerk Docs.
The incident is now resolved
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.
All systems are functional
Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.
Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.
Clerk’s official status page says: Partial System Degradation. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Clerk reported was “Issues with Documentation "Ask AI"”, today (2026-10-21 23:50 UTC). None of its incidents in the last 90 days were a full outage.
Clerk reports 16 components on its status page, including Authentication & User, Machine authentication, Webhooks, Hosted UIs (Account Portal), Session management. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Hosted UIs (the Account Portal) are a separate component from the Authentication API. The API can be fine while the hosted sign-in page fails — check that row on the status page.
Email delivery and SMS delivery are their own components, tracked separately from session management and the core API. Look at those rows rather than the API status.
If the status above is operational but Clerk still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.