User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Clerk.io down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → clerk.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 27 min ago. Last stored result reached it in 859 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 749 ms | 0 |
| Nov 7 | 0 | 0.0 | 875 ms | 0 |
| Nov 7 | 0 | 0.0 | 795 ms | 0 |
| Nov 7 | 0 | 0.0 | 867 ms | 0 |
| Nov 7 | 0 | 0.0 | 857 ms | 0 |
| Nov 8 | 0 | 0.0 | 827 ms | 0 |
| Nov 8 | 0 | 0.0 | 800 ms | 0 |
| Nov 8 | 0 | 0.0 | 782 ms | 0 |
| Nov 8 | 0 | 0.0 | 779 ms | 0 |
| Nov 9 | 0 | 0.0 | 862 ms | 0 |
| Nov 9 | 0 | 0.0 | 835 ms | 0 |
| Nov 9 | 0 | 0.0 | 826 ms | 0 |
| Nov 9 | 0 | 0.0 | 828 ms | 0 |
| Nov 10 | 0 | 0.0 | 808 ms | 0 |
| Nov 10 | 0 | 0.0 | 805 ms | 0 |
| Nov 10 | 0 | 0.0 | 817 ms | 0 |
| Nov 10 | 0 | 0.0 | 836 ms | 0 |
| Nov 11 | 0 | 0.0 | 809 ms | 0 |
| Nov 11 | 0 | 0.0 | 781 ms | 0 |
| Nov 11 | 0 | 0.0 | 825 ms | 0 |
| Nov 11 | 0 | 0.0 | 849 ms | 0 |
| Nov 12 | 0 | 0.0 | 852 ms | 0 |
| Nov 12 | 0 | 0.0 | 868 ms | 0 |
| Nov 12 | 0 | 0.0 | 877 ms | 0 |
| Nov 12 | 0 | 0.0 | 792 ms | 0 |
| Nov 13 | 0 | 0.0 | 765 ms | 0 |
| Nov 13 | 0 | 0.0 | 822 ms | 0 |
| Nov 13 | 0 | 0.0 | 799 ms | 0 |
| Nov 13 | 0 | 0.0 | 843 ms | 0 |
| Nov 14 | 0 | 0.0 | 885 ms | 0 |
| Nov 14 | 0 | 0.0 | 865 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Clerk.io badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Clerk.io yet. Outages of 10 minutes or more get their own page here.
Having trouble with Clerk.io?
One report per service every 10 minutes from this network. No account.
Follow Clerk.io
Get an email when Clerk.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clerk.io alerts to Slack, Discord or a webhook — free.
About Clerk.io
We track Clerk.io (clerk.io) as part of the AI group. You already pay to bring shoppers to your store. Clerk.io helps them find the right products, grow their baskets and come back with AI Search, Recommendations, Chat, Audience and Email.
Clerk.io publishes an official status page at status.clerk.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 861 ms average, 785–955 ms range across 16 successful checks.
Questions
Is Clerk.io down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Clerk.io last down?
We have not recorded a public Clerk.io incident since monitoring began 9 days ago.
What is Clerk.io's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Clerk.io respond?
861 ms on average over the last 24 hours (785–955 ms).
Does Clerk.io have an official status page?
Yes, at https://status.clerk.io.
Clerk.io not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Clerk.io here at once, the problem is on Clerk.io's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Clerk.io. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.