User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
clerk.chat · AI
Is Clerk Chat 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.chat—
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 46 min ago. Last stored result reached it in 62 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 |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 99 ms | 0 |
| Tue 06 | 0 | 0.0 | 322 ms | 0 |
| Tue 08 | 0 | 0.0 | 81 ms | 0 |
| Tue 10 | 0 | 0.0 | 202 ms | 0 |
| Tue 12 | 0 | 0.0 | 81 ms | 0 |
| Tue 14 | 0 | 0.0 | 173 ms | 0 |
| Tue 17 | 0 | 0.0 | 136 ms | 0 |
| Tue 19 | 0 | 0.0 | 186 ms | 0 |
| Tue 21 | 0 | 0.0 | 53 ms | 0 |
| Wed 00 | 0 | 0.0 | 88 ms | 0 |
| Wed 02 | 0 | 0.0 | 256 ms | 0 |
| Wed 04 | 0 | 0.0 | 90 ms | 0 |
| Wed 06 | 0 | 0.0 | 90 ms | 0 |
| Wed 08 | 0 | 0.0 | 66 ms | 0 |
| Wed 11 | 0 | 0.0 | 244 ms | 0 |
| Wed 12 | 0 | 0.0 | 285 ms | 0 |
| Wed 14 | 0 | 0.0 | 111 ms | 0 |
| Wed 16 | 0 | 0.0 | 104 ms | 0 |
| Wed 18 | 0 | 0.0 | 205 ms | 0 |
| Wed 21 | 0 | 0.0 | 98 ms | 0 |
| Wed 23 | 0 | 0.0 | 100 ms | 0 |
| Thu 01 | 0 | 0.0 | 89 ms | 0 |
| Thu 03 | 0 | 0.0 | 109 ms | 0 |
| Thu 05 | 0 | 0.0 | 106 ms | 0 |
| Thu 07 | 0 | 0.0 | 284 ms | 0 |
| Thu 09 | 0 | 0.0 | 83 ms | 0 |
| Thu 11 | 0 | 0.0 | 102 ms | 0 |
| Thu 13 | 0 | 0.0 | 179 ms | 0 |
| Thu 15 | 0 | 0.0 | 75 ms | 0 |
| Thu 17 | 0 | 0.0 | 116 ms | 0 |
| Thu 19 | 0 | 0.0 | 90 ms | 0 |
| Thu 21 | 0 | 0.0 | 93 ms | 0 |
| Fri 00 | 0 | 0.0 | 64 ms | 0 |
| Fri 01 | 0 | 0.0 | 266 ms | 0 |
| Fri 03 | 0 | 0.0 | 116 ms | 0 |
| Fri 05 | 0 | 0.0 | 57 ms | 0 |
| Fri 07 | 0 | 0.0 | 72 ms | 0 |
| Fri 09 | 0 | 0.0 | 86 ms | 0 |
| Fri 11 | 0 | 0.0 | 81 ms | 0 |
| Fri 13 | 0 | 0.0 | 333 ms | 0 |
| Fri 15 | 0 | 0.0 | 69 ms | 0 |
| Fri 17 | 0 | 0.0 | 84 ms | 0 |
| Fri 18 | 0 | 0.0 | 78 ms | 0 |
| Fri 19 | 0 | 0.0 | 1552 ms | 0 |
| Fri 21 | 0 | 0.0 | 126 ms | 0 |
| Fri 23 | 0 | 0.0 | 207 ms | 0 |
| Sat 00 | 0 | 0.0 | 151 ms | 0 |
| Sat 02 | 0 | 0.0 | 62 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Clerk Chat 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 Chat yet. Outages of 10 minutes or more get their own page here.
Having trouble with Clerk Chat?
One report per service every 10 minutes from this network. No account.
Follow Clerk Chat
Get an email when Clerk Chat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clerk Chat alerts to Slack, Discord or a webhook — free.
About Clerk Chat
We track Clerk Chat (clerk.chat) as part of the AI group. Add unlimited SMS, MMS, RCS, WhatsApp, and eFax to your Teams numbers. Replace expensive Microsoft Calling Plans with Operator Connect. Deploy AI voice and…
Clerk Chat publishes an official status page at status.clerk.chat; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 220 ms average, 57–1552 ms range across 14 successful checks.
Questions
Is Clerk Chat down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Clerk Chat last down?
We have not recorded a public Clerk Chat incident since monitoring began 8 days ago.
What is Clerk Chat's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Clerk Chat respond?
220 ms on average over the last 24 hours (57–1552 ms).
Does Clerk Chat have an official status page?
Yes, at https://status.clerk.chat.
Clerk Chat 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 Chat here at once, the problem is on Clerk Chat'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 Chat. 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.