https://approjects-vendor-status-watch.static.hf.space/v/clerk.htmlIncidents from Clerk's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://status.clerk.comclerk:2026-09-04T10:06:09ZFri, 04 Sep 2026 10:06:09 +0000Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.https://status.clerk.comclerk:2026-09-01T15:48:03ZTue, 01 Sep 2026 15:48:03 +0000Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.https://status.clerk.comclerk:2026-08-31T13:55:24ZMon, 31 Aug 2026 13:55:24 +0000API performance has remained stable following mitigation. This incident has been resolved.https://status.clerk.comclerk:2026-08-04T23:03:58ZTue, 04 Aug 2026 23:03:58 +0000We've resolved the issue with our upstream provider.https://status.clerk.comclerk:2026-08-01T10:00:01ZSat, 01 Aug 2026 10:00:01 +0000All systems are operationalhttps://status.clerk.comclerk:2026-07-31T12:23:58ZFri, 31 Jul 2026 12:23:58 +0000Custom domain provisioning is fully operational againhttps://status.clerk.comclerk:2026-07-16T13:04:44ZThu, 16 Jul 2026 13:04:44 +0000We have confirmed that error rates have returned to baseline.https://status.clerk.comclerk:2026-07-16T07:56:30ZThu, 16 Jul 2026 07:56:30 +0000There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.https://status.clerk.comclerk:2026-07-12T22:05:48ZSun, 12 Jul 2026 22:05:48 +0000All domains have been processed from this incident.https://status.clerk.comclerk:2026-07-09T20:38:10ZThu, 09 Jul 2026 20:38:10 +0000The underlying issue has been identified and the Account Portal is now fully functioning again.https://status.clerk.comclerk:2026-07-01T17:12:21ZWed, 01 Jul 2026 17:12:21 +0000We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.https://status.clerk.comclerk:2026-06-18T20:21:29ZThu, 18 Jun 2026 20:21:29 +0000A fix has been published and confirmed it's now resolving SVGs correctlyhttps://status.clerk.comclerk:2026-06-18T15:43:35ZThu, 18 Jun 2026 15:43:35 +0000Services are up and running.https://status.clerk.comclerk:2026-06-15T15:44:49ZMon, 15 Jun 2026 15:44:49 +0000Systems are fully operationalhttps://status.clerk.comclerk:2026-06-12T14:48:30ZFri, 12 Jun 2026 14:48:30 +0000All systems are operationalhttps://status.clerk.comclerk:2026-06-09T21:56:49ZTue, 09 Jun 2026 21:56:49 +0000Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruptionhttps://status.clerk.comclerk:2026-05-28T19:16:05ZThu, 28 May 2026 19:16:05 +0000APIs have returned to normal operation.https://status.clerk.comclerk:2026-05-26T21:19:09ZTue, 26 May 2026 21:19:09 +0000The root cause has been identified and addressed. We will continue to monitor going forward.https://status.clerk.comclerk:2026-05-22T15:48:01ZFri, 22 May 2026 15:48:01 +0000Systems are back to normal.https://status.clerk.comclerk:2026-05-14T20:37:28ZThu, 14 May 2026 20:37:28 +0000The upstream provider marked the issue as resolved, we're continuing to monitor the database, but no error was observed.https://status.clerk.comclerk:2026-05-11T15:00:40ZMon, 11 May 2026 15:00:40 +0000The issue has been resolved.https://status.clerk.comclerk:2026-05-08T11:02:35ZFri, 08 May 2026 11:02:35 +0000We continue to work with our DNS provider to discover the source of the issue. We currently believe approximately 0.37% of traffic was impacted by being unable to resolve DNS of the CDN that provides ClerkJS.https://status.clerk.comclerk:2026-05-08T01:39:36ZFri, 08 May 2026 01:39:36 +0000We have identified the root cause and are putting in place mitigations to ensure this does not happen in the future.https://status.clerk.comclerk:2026-04-27T18:43:49ZMon, 27 Apr 2026 18:43:49 +0000The issue has been resolvedhttps://status.clerk.comclerk:2026-04-26T07:39:28ZSun, 26 Apr 2026 07:39:28 +0000The issue has been resolvedhttps://status.clerk.comclerk:2026-04-25T08:00:34ZSat, 25 Apr 2026 08:00:34 +0000Development services are back to normal.