Vendor Status Watch

← all vendors

Clerk status history

Current state: operational — “All Systems Operational” per https://status.clerk.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
13incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:

How long do Clerk incidents last?

48 minmedian incident duration24 measured
4.6 h90th percentile1 in 10 ran longer
102 minmedian, major/critical only6 incidents

From 24 incidents with a vendor-posted start and resolve time. Longest on record: Intermittent Issues with Development Services — 6.9 h (2026-04-25 08:00 UTC). Excluded, never estimated: 2 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (26)

StartedIncidentStatusImpactDuration
2026-09-04 10:06 UTCDelayed email delivery to Microsoft (Outlook / Microsoft 365) recipientsresolvedminor4 h 34 min
2026-09-01 15:48 UTCGCP incident in us-central1-bresolvedminor3 h 25 min
2026-08-31 13:55 UTCElevated API latencyresolvedminor1 h 44 min
2026-08-04 23:03 UTCIncreased API latency and errorsresolvedminor36 min
2026-08-01 10:00 UTCIncreased error rateresolvedminor4 min
2026-07-31 12:23 UTCElevated error rate in domain provisioningresolvedminor36 min
2026-07-16 13:04 UTCElevated API Errorsresolvedminor56 min
2026-07-16 07:56 UTCIncreased latency on our APIsresolvedminor1 min
2026-07-12 22:05 UTCElevated errors while configuring domainsresolvedmajor3 h 31 min
2026-07-09 20:38 UTCElevated errors in Account Portalresolvedminor5 min
2026-07-01 17:12 UTCDelay in webhook deliveryresolvedminor14 min
2026-06-18 20:21 UTCSVGs are not loading properlyresolvedminor2 min
2026-06-18 15:43 UTCDashboard analytics not loading properlyresolvedminor34 min
2026-06-15 15:44 UTCElevated errors on Platform-APIresolvedminor
2026-06-12 14:48 UTCElevated errors or delays for Clerk application going liveresolvedminor40 min
2026-06-09 21:56 UTCAnalytics API I/O timeoutsresolvedmajor40 min
2026-05-28 19:16 UTCElevated Errors in APIsresolvedminor1 h 16 min
2026-05-26 21:19 UTCElevated 500 rates on API responsesresolvedmajor1 h 07 min
2026-05-22 15:48 UTCIssue with Provisioning Domainsresolvedminor5 h 55 min
2026-05-14 20:37 UTCSCIM services are facing intermittent errorsresolvedminor28 min
2026-05-11 15:00 UTCAccount Portal not Redirectingresolvedmajor2 h 18 min
2026-05-08 11:02 UTCSign-in Clerk components unavailable for some domainsresolvedminor3 h 38 min
2026-05-08 01:39 UTCDashboard downresolvedcritical37 min
2026-04-27 18:43 UTCIncreased error rateresolvedminor2 h 35 min
2026-04-26 07:39 UTC/handshake endpoint failuresresolvedminor
2026-04-25 08:00 UTCIntermittent Issues with Development Servicesresolvedmajor6 h 52 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Clerk with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "clerk"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}