Is Clerk down in the US?
Vendor reports no incidentWhat Clerk reports
Clerk reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:05 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn, San Jose, and Chicago
All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked Clerk at Nov 5, 2026, 5:19 PM UTC.
Over the last 24 hours we completed 326 checks from Ashburn, San Jose, and Chicago and 326 answered cleanly, 100.00% availability.
Of the 7 other regions we check Clerk from, all 7 read checks passing right now.
Email me when Clerk reports an incident on its status page, and again when it reports it resolved.
What our Ashburn, San Jose, and Chicago probes measured
Last checked Nov 5, 2026, 5:19 PM UTC.
Clerk from Ashburn, San Jose, and Chicago over the last 30 days
Over the last 30 days, Clerk answered our Ashburn probe in 588 ms on average, and 1 check in 20 took longer than 976 ms.
Over the last 30 days, Clerk answered our Chicago probe in 757 ms on average, and 1 check in 20 took longer than 1,216 ms.
Over the last 30 days, Clerk answered our San Jose probe in 781 ms on average, and 1 check in 20 took longer than 1,222 ms.
Ranked by average response time across the 10 cities we check Clerk from, Ashburn 3rd, Chicago 6th, San Jose 7th; Frankfurt was fastest at 584 ms and Singapore slowest at 1,069 ms.
From Ashburn, San Jose, and Chicago we ran 10,577 checks of Clerk in 30 days, and 10,575 answered cleanly: 99.98% availability.
2 of the 30 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.68% across 321 checks.
In Ashburn local time (EST), Clerk was slowest around 1 PM, at 709 ms on average over the last 14 days, and quickest around 11 PM, at 491 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 235 | 100.00% | 835 ms |
| Wed, Nov 4 | 326 | 100.00% | 969 ms |
| Tue, Nov 3 | 321 | 99.68% | 1,013 ms |
| Mon, Nov 2 | 344 | 100.00% | 1,099 ms |
| Sun, Nov 1 | 360 | 100.00% | 744 ms |
| Sat, Oct 31 | 360 | 100.00% | 487 ms |
| Fri, Oct 30 | 359 | 100.00% | 498 ms |
| Thu, Oct 29 | 362 | 100.00% | 787 ms |
| Wed, Oct 28 | 358 | 100.00% | 778 ms |
| Tue, Oct 27 | 360 | 100.00% | 817 ms |
| Mon, Oct 26 | 359 | 99.72% | 775 ms |
| Sun, Oct 25 | 359 | 100.00% | 666 ms |
| Sat, Oct 24 | 360 | 100.00% | 739 ms |
| Fri, Oct 23 | 360 | 100.00% | 741 ms |
Clerk outages measured from the US
Our Ashburn, San Jose, and Chicago probes measured no confirmed Clerk outage in the last 90 days.
How the other regions read right now
Of the 7 other regions we check Clerk from, all 7 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 100 checks |
| Tokyo | Checks passing | 100.00% of 61 checks |
| Toronto | Checks passing | 100.00% of 72 checks |
| London | Checks passing | 100.00% of 72 checks |
| Singapore | Checks passing | 100.00% of 71 checks |
| Sydney | Checks passing | 100.00% of 71 checks |
| São Paulo | Checks passing | 100.00% of 72 checks |
Other countries we check Clerk from
How we measured this
The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against Clerk's public endpoints. They are not user reports, and they are not Clerk's own status page.
See Clerk's full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter