Is Clerk down?
Right now
Partly. Clerk is degraded.
Development instances only - Apple rejecting emails.
Read from status.clerk.com · every 120s
For agents
proceed
Proceed, expect slow or flaky responses.
GET upbutler.com/status/clerk/status.agent.json
MCP: upstream_status {"service":"clerk"}
Hosted sign-in, sessions and user management. An outage locks every user out even though your own servers are healthy.
What Clerk reports
Degraded· 1 open incident
Taken as is from Clerk's own status page API. Incident titles and component names below are theirs.
Open status.clerk.comUpButler's independent probe
Backend API is answeringHTTP 401 · 171 ms
One request without credentials to api.clerk.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Open at Clerk
- Development instances only - Apple rejecting emailsidentified · impact minor
Since
We discovered today that emails sent only from development instances to Apple email addresses (icloud.com, me.com) are being rejected by Apple. We have reached out to Apple to inquire further and are hoping for a swift resolution on their end. In the meantime, we recommend using test emails ( ) or an email address from a non-Apple domain to test/send emails from your development instances.
Text written by Clerk, shown unchanged.
Clerk components
1 of 15 not operational
- Authentication & UserOperational
- Machine authenticationOperational
- WebhooksOperational
- Hosted UIs (Account Portal)Operational
- Session managementOperational
- Multi-tenant authenticationOperational
- SCIMOperational
- BillingOperational
- Email deliveryDegraded
- SMS deliveryOperational
- DashboardOperational
- Dashboard analyticsOperational
- Dashboard searchOperational
- Application "Go live"Operational
- Platform APIOperational
Clerk incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Dashboard increased latency | minor | 14 h 19 min |
Tell your outage from Clerk's
Declare that your project depends on Clerk. When one of your monitors fails while Clerk has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- clerkcurl -s https://upbutler.com/status/clerk/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "clerk",
"verdict": "proceed",
"status": "degraded",
"reason": "Development instances only - Apple rejecting emails",
"retryAfterSec": null,
"incident": {
"title": "Development instances only - Apple rejecting emails",
"url": "https://status.clerk.com/incidents/01M3M9SSWNTTRMRDFV59B28GCB"
},
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Clerk down right now?
- Partly. As of 2026-10-10 05:12 UTC, Clerk is degraded, with an open incident: "Development instances only - Apple rejecting emails". This page reads the status again every 2 minutes.
- Where does this status come from?
- From Clerk's own status page API at https://status.clerk.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Clerk's words.
- What does UpButler's own Clerk check prove?
- Every two minutes UpButler sends one request without credentials to the Clerk Backend API (api.clerk.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Clerk reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Clerk status?
- Fetch https://upbutler.com/status/clerk/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"clerk"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Clerk's?
- Add "clerk" to the dependencies of your UpButler workspace. When one of your monitors fails while Clerk has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in authentication
UpButler is not affiliated with Clerk. Status and incident text belong to Clerk and are read from their public status source; the probe result is UpButler's own measurement.