Skip to content

Outage tracker / Clerk

Is Clerk down?

I'm having a problem

Operationalchecked moments ago

We reached Clerk from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Clerk answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Clerk (since Aug 22, 2026).

Clerk reports an active incident: "Development instances only - Apple rejecting emails" (minor incident, since Sep 28, 2026, 3:23 PM UTC). That is their claim, not our measurement: our probes are currently reaching Clerk, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East287 msOperational
US-West582 msOperational
Europe494 msOperational
Asia-Pacific574 msOperational
US-Central693 msOperational
Canada786 msOperational
UK677 msOperational
Southeast Asia938 msOperational
Australia1108 msOperational
South America1010 msOperational
their status pagetheir claim, not our reading

Clerk reports: Minor incident (“Partial System Degradation”)

from Clerk's own status page, checked Oct 5, 2026, 7:58 PM UTC

Clerk reports an active incident: Development instances only - Apple rejecting emails (minor incident, since Sep 28, 2026, 3:23 PM UTC)

Clerk's status page reports Partial System Degradation. Our probes are currently reaching Clerk successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Clerk's own component breakdown, as they publish it

  • Authentication & UserOperational
  • Machine authenticationOperational
  • WebhooksOperational
  • Hosted UIs (Account Portal)Operational
  • Session managementOperational
  • Multi-tenant authenticationOperational
  • SCIMOperational
  • BillingOperational
  • Email deliveryDegraded performance
  • SMS deliveryOperational
  • DashboardOperational
  • Dashboard analyticsOperational
  • Dashboard searchOperational
  • Application "Go live"Operational
  • Platform APIOperational

These are Clerk's components, named and scored by Clerk. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Clerk's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Clerk response time, by region

US-East
756msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 708ms2026-09-07 UTC: p95 841ms2026-09-08 UTC: p95 772ms2026-09-09 UTC: p95 757ms2026-09-10 UTC: p95 698ms2026-09-11 UTC: p95 855ms2026-09-12 UTC: p95 836ms2026-09-13 UTC: p95 858ms2026-09-14 UTC: p95 808ms2026-09-15 UTC: p95 832ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 753ms2026-09-21 UTC: p95 783ms2026-09-22 UTC: p95 706ms2026-09-23 UTC: p95 638ms2026-09-24 UTC: p95 631ms2026-09-25 UTC: p95 566ms2026-09-26 UTC: p95 661ms2026-09-27 UTC: p95 637ms2026-09-28 UTC: p95 660ms2026-09-29 UTC: p95 851ms2026-09-30 UTC: p95 757ms2026-10-01 UTC: p95 883ms2026-10-02 UTC: p95 681ms2026-10-03 UTC: p95 828ms2026-10-04 UTC: p95 716ms2026-10-05 UTC: p95 756ms
Sep 6Sep 20Oct 5
US-West
767msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 737ms2026-09-07 UTC: p95 674ms2026-09-08 UTC: p95 637ms2026-09-09 UTC: p95 355ms2026-09-10 UTC: p95 671ms2026-09-11 UTC: p95 793ms2026-09-12 UTC: p95 693ms2026-09-13 UTC: p95 577ms2026-09-14 UTC: p95 665ms2026-09-15 UTC: p95 833ms2026-09-16 UTC: p95 948ms2026-09-17 UTC: p95 993ms2026-09-18 UTC: p95 998ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 806ms2026-09-22 UTC: p95 743ms2026-09-23 UTC: p95 664ms2026-09-24 UTC: p95 901ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 902ms2026-09-27 UTC: p95 882ms2026-09-28 UTC: p95 838ms2026-09-29 UTC: p95 758ms2026-09-30 UTC: p95 867ms2026-10-01 UTC: p95 919ms2026-10-02 UTC: p95 978ms2026-10-03 UTC: p95 860ms2026-10-04 UTC: p95 764ms2026-10-05 UTC: p95 767ms
Sep 6Sep 20Oct 5
Europe
1.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 755ms2026-09-07 UTC: p95 790ms2026-09-08 UTC: p95 749ms2026-09-09 UTC: p95 756ms2026-09-10 UTC: p95 768ms2026-09-11 UTC: p95 787ms2026-09-12 UTC: p95 782ms2026-09-13 UTC: p95 869ms2026-09-14 UTC: p95 884ms2026-09-15 UTC: p95 882ms2026-09-16 UTC: p95 897ms2026-09-17 UTC: p95 938ms2026-09-18 UTC: p95 997ms2026-09-19 UTC: p95 953ms2026-09-20 UTC: p95 925ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 977ms2026-09-25 UTC: p95 928ms2026-09-26 UTC: p95 910ms2026-09-27 UTC: p95 833ms2026-09-28 UTC: p95 940ms2026-09-29 UTC: p95 912ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 811ms2026-10-02 UTC: p95 863ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Asia-Pacific
740msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 554ms2026-09-07 UTC: p95 596ms2026-09-08 UTC: p95 697ms2026-09-09 UTC: p95 763ms2026-09-10 UTC: p95 716ms2026-09-11 UTC: p95 738ms2026-09-12 UTC: p95 874ms2026-09-13 UTC: p95 617ms2026-09-14 UTC: p95 661ms2026-09-15 UTC: p95 545ms2026-09-16 UTC: p95 674ms2026-09-17 UTC: p95 789ms2026-09-18 UTC: p95 805ms2026-09-19 UTC: p95 655ms2026-09-20 UTC: p95 726ms2026-09-21 UTC: p95 966ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 821ms2026-09-24 UTC: p95 885ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 993ms2026-09-27 UTC: p95 808ms2026-09-28 UTC: p95 754ms2026-09-29 UTC: p95 694ms2026-09-30 UTC: p95 755ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 724ms2026-10-03 UTC: p95 684ms2026-10-04 UTC: p95 697ms2026-10-05 UTC: p95 740ms
Sep 6Sep 20Oct 5
US-Central
977msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 994ms2026-09-08 UTC: p95 999ms2026-09-09 UTC: p95 939ms2026-09-10 UTC: p95 986ms2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 993ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 981ms2026-09-16 UTC: p95 955ms2026-09-17 UTC: p95 972ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 991ms2026-09-21 UTC: p95 928ms2026-09-22 UTC: p95 921ms2026-09-23 UTC: p95 906ms2026-09-24 UTC: p95 900ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 997ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 935ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 945ms2026-10-02 UTC: p95 928ms2026-10-03 UTC: p95 953ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 977ms
Sep 6Sep 20Oct 5
Canada
1.0sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 810ms2026-09-11 UTC: p95 966ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 917ms2026-09-15 UTC: p95 687ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
UK
819msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 838ms2026-09-07 UTC: p95 904ms2026-09-08 UTC: p95 788ms2026-09-09 UTC: p95 753ms2026-09-10 UTC: p95 742ms2026-09-11 UTC: p95 790ms2026-09-12 UTC: p95 755ms2026-09-13 UTC: p95 856ms2026-09-14 UTC: p95 756ms2026-09-15 UTC: p95 778ms2026-09-16 UTC: p95 830ms2026-09-17 UTC: p95 837ms2026-09-18 UTC: p95 803ms2026-09-19 UTC: p95 805ms2026-09-20 UTC: p95 782ms2026-09-21 UTC: p95 738ms2026-09-22 UTC: p95 795ms2026-09-23 UTC: p95 764ms2026-09-24 UTC: p95 812ms2026-09-25 UTC: p95 932ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 981ms2026-09-29 UTC: p95 880ms2026-09-30 UTC: p95 850ms2026-10-01 UTC: p95 903ms2026-10-02 UTC: p95 828ms2026-10-03 UTC: p95 880ms2026-10-04 UTC: p95 845ms2026-10-05 UTC: p95 819ms
Sep 6Sep 20Oct 5
Southeast Asia
961msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 973ms2026-09-12 UTC: p95 922ms2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 996ms2026-10-05 UTC: p95 961ms
Sep 6Sep 20Oct 5
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 921ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 966ms2026-09-12 UTC: p95 892ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 895ms2026-09-15 UTC: p95 867ms2026-09-16 UTC: p95 760ms2026-09-17 UTC: p95 745ms2026-09-18 UTC: p95 832ms2026-09-19 UTC: p95 896ms2026-09-20 UTC: p95 836ms2026-09-21 UTC: p95 903ms2026-09-22 UTC: p95 840ms2026-09-23 UTC: p95 563ms2026-09-24 UTC: p95 696ms2026-09-25 UTC: p95 827ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 936ms2026-09-29 UTC: p95 665ms2026-09-30 UTC: p95 668ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 500ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 845ms2026-09-07 UTC: p95 756ms2026-09-08 UTC: p95 856ms2026-09-09 UTC: p95 676ms2026-09-10 UTC: p95 810ms2026-09-11 UTC: p95 870ms2026-09-12 UTC: p95 976ms2026-09-13 UTC: p95 917ms2026-09-14 UTC: p95 858ms2026-09-15 UTC: p95 910ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 798ms2026-09-22 UTC: p95 800ms2026-09-23 UTC: p95 642ms2026-09-24 UTC: p95 711ms2026-09-25 UTC: p95 907ms2026-09-26 UTC: p95 928ms2026-09-27 UTC: p95 844ms2026-09-28 UTC: p95 696ms2026-09-29 UTC: p95 753ms2026-09-30 UTC: p95 828ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 640ms2026-10-03 UTC: p95 848ms2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5

Is it Clerk, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Clerk -- it cannot diagnose Clerk's own systems.

What we measured, function by function

Clerk answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Clerk go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Clerk, and again when they can reach it again. That is our own measurement from ten regions, not Clerk's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 287msstatus code: 401checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Clerk normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 582msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Clerk normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 693msstatus code: 401checked: Oct 5, 2026, 8:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Clerk normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 786msstatus code: 401checked: Oct 5, 2026, 7:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Clerk normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1010msstatus code: 401checked: Oct 5, 2026, 8:16 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Clerk normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 494msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Clerk normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 677msstatus code: 401checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Clerk normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 574msstatus code: 401checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Clerk normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 938msstatus code: 401checked: Oct 5, 2026, 8:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Clerk normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1108msstatus code: 401checked: Oct 5, 2026, 8:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Clerk normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Clerk, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Clerk yet, which is not evidence that nothing is wrong.

Recent outages

Dashboard increased latency, 14h 19mdeclared on their status page2026-10-01
Development instances only - Apple rejecting emailsdeclared on their status page2026-09-28
Delays in webhook delivery, 1h 8mdeclared on their status page2026-09-16
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients, 4h 34mdeclared on their status page2026-09-04
GCP incident in us-central1-b, 3h 26mdeclared on their status page2026-09-01
Elevated API latency, 1h 45mdeclared on their status page2026-08-31
Increased API latency and errors, 37mdeclared on their status page2026-08-04
Increased error rate, 5mdeclared on their status page2026-08-01

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Clerk since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Clerk covering any window you pick, with our measurements and Clerk's own claim at the time, side by side.

Full availability history for Clerk: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

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 servers

Put this badge in your README

Clerk uptime measured by RealUptimeLive, from this page's own readings.
[![Clerk uptime measured by RealUptime](https://realuptime.io/outages/clerk/badge.svg?days=30)](https://realuptime.io/outages/clerk)
<a href="https://realuptime.io/outages/clerk"><img src="https://realuptime.io/outages/clerk/badge.svg?days=30" alt="Clerk uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Clerk's SLA implies, from our measurement

At or above your target

We measured none of downtime for Clerk over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Clerk's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.clerk.com/v1/users
secondary
https://clerk.com/
secondary
https://status.clerk.com/api/v2/status.json
RealUptime is not affiliated with Clerk; the name identifies what we measured, and nothing here speaks for Clerk's own team. We send a single web request to Clerk from 10 regions on our own schedule and time the response. We do not see inside Clerk's systems, do not use an account or real transaction, and are not the same signal Clerk's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Clerk is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.