Clerk's API is responding
Last checked from Europe at (HTTP 401 in 274 ms).
This checks the API that operates Clerk. It covers the control plane, not customer workloads running on it.
What we check: GET https://api.clerk.com/v1/users every 5 minutes, expecting HTTP 401. A failure is only reported after a second region and a 30-second re-check agree.
Uptime and downtime
Uptime is (successful checks ÷ all counted checks) over our own scheduled checks from Europe. Downtime is sample-derived at the same 5-minute resolution: every confirmed failed check counts as 5 minutes of downtime, except isolated blips, which count against uptime but not against downtime or the incident count. Blocked or unconfirmed checks are excluded rather than guessed.
Response time
Amber line: median (p50) of successful checks per hour (per day on the 30-day view). Thin line: p95. Measured from Europe; a single vantage point, so treat the absolute numbers as relative.
Outage history from our checks
- No incidents or blips detected by our probes in the last 30 days.
A blip is a single confirmed failed check with successful checks either side; it appears here but is excluded from the incident count and the downtime figure above (it still counts against the uptime percentage). Durations are quantised to our 5-minute check interval, so they usually read slightly longer than the vendor's own figures.
Official status from Clerk
- resolved Elevated error rates for authentication requests minor
- resolved SMS Delivery Issues major
- resolved Issues with Documentation "Ask AI" minor
- resolved Dashboard increased latency minor
- resolved Development instances only - Apple rejecting emails minor
- resolved Delays in webhook delivery minor
- resolved Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients minor
- resolved GCP incident in us-central1-b minor
- resolved Elevated API latency minor
- resolved Increased API latency and errors minor
Source: status.clerk.com, refreshed every 10 minutes. These entries are Clerk's own reports, not our findings. The gap between our probes failing and the vendor acknowledging it is usually the moment you are searching.
It says up, but you still can't reach Clerk?
A global check passing and your request failing are not contradictory. Work outward from your machine:
- Try another network. Switch to mobile data or a phone hotspot. If it works there, the problem is your office/home network, VPN or corporate proxy, not Clerk.
- Disconnect your VPN. Corporate and consumer VPNs exit from IP ranges that get rate-limited or blocked by bot protection; Clerk may be refusing that exit node specifically.
- Flush your DNS cache (
ipconfig /flushdnson Windows,sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderon macOS,resolvectl flush-cacheson systemd Linux) or point your resolver at 1.1.1.1 / 8.8.8.8 temporarily. - Check your clock. TLS handshakes fail with confusing errors when the system time is minutes off.
- Check the region. Our probes run from Europe and US East. A CDN or regional edge failure elsewhere can affect you and not us. Try our website down checker against the exact URL you are using.
- Check whether it's your account, not the service. API keys expiring, quota limits and suspended workspaces produce 401/403/429 responses that look like outages from inside an app.
Frequently asked questions
Is Clerk down right now?
Clerk's API is responding. Last checked from Europe at 12:32 UTC (HTTP 401 in 274 ms). This verdict comes from Drumbeats' own automated checks, run every 5 minutes from Europe and confirmed from US East before any failure is reported.
What exactly does Drumbeats check for Clerk?
We send a GET request to https://api.clerk.com/v1/users and expect HTTP 401. This checks the API that operates Clerk. It covers the control plane, not customer workloads running on it.
Does "Clerk's API is up" mean every part of Clerk works?
No. This checks the API that operates Clerk. It covers the control plane, not customer workloads running on it. A green verdict here means the endpoint we probe answered as expected; an outage in a part of Clerk we do not probe can still affect you. Check Clerk's own status page for component-level detail.
Why do your outage durations differ from Clerk's own status page?
We sample every 5 minutes, so our durations are quantised to 5-minute steps and the shortest outage we can observe is one check interval. Clerk's own numbers come from internal monitoring with far finer resolution, and vendors often start the clock when they acknowledge an incident rather than when it began. Both views are shown on this page, clearly separated.
Is this page affiliated with Clerk?
No. Drumbeats is not affiliated with, endorsed by or a partner of Clerk. This page reflects independent automated checks from our own infrastructure, plus incidents Clerk publishes on its own status page, shown separately and linked to the source.
How checks, confirmation, blips and uptime work is explained once on the hub page.
Related services
Monitor your own services the same way
Uptime checks from multiple regions, cron and background-job heartbeats, and alerts to Slack, email or webhooks. Free for up to 50 monitors.
Start monitoring free