Clerk Outage History

53 incidents recorded over the last 365 days, 53 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Clerk status99.38% uptime history

Every Recorded Clerk Incident

Clerk incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 4, 2026Increased API latency and errorsWe've resolved the issue with our upstream provider.36 minResolved
Aug 1, 2026Increased error rateAll systems are operational4 minResolved
Jul 31, 2026Elevated error rate in domain provisioningCustom domain provisioning is fully operational again36 minResolved
Jul 16, 2026Elevated API ErrorsWe have confirmed that error rates have returned to baseline.56 minResolved
Jul 16, 2026Increased latency on our APIsThere 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.1 minResolved
Jul 12, 2026Elevated errors while configuring domainsAll domains have been processed from this incident.3h 31mResolved
Jul 9, 2026Elevated errors in Account PortalThe underlying issue has been identified and the Account Portal is now fully functioning again.5 minResolved
Jul 1, 2026Delay in webhook deliveryWe have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.14 minResolved
Jun 18, 2026SVGs are not loading properlyA fix has been published and confirmed it's now resolving SVGs correctly2 minResolved
Jun 18, 2026Dashboard analytics not loading properlyServices are up and running.34 minResolved
Jun 15, 2026Elevated errors on Platform-APISystems are fully operational-18 minResolved
Jun 12, 2026Elevated errors or delays for Clerk application going liveAll systems are operational40 minResolved
Jun 9, 2026Analytics API I/O timeoutsBetween 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…40 minResolved
May 28, 2026Elevated Errors in APIsAPIs have returned to normal operation.1h 16mResolved
May 26, 2026Elevated 500 rates on API responsesThe root cause has been identified and addressed. We will continue to monitor going forward.1h 7mResolved
May 22, 2026Issue with Provisioning DomainsSystems are back to normal.5h 55mResolved
May 20, 2026SCIM Database upgrade1799h 20mResolved
May 14, 2026SCIM services are facing intermittent errorsThe upstream provider marked the issue as resolved, we're continuing to monitor the database, but no error was observed.28 minResolved
May 11, 2026Account Portal not RedirectingThe issue has been resolved.2h 18mResolved
May 8, 2026Sign-in Clerk components unavailable for some domainsWe 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.3h 38mResolved
May 8, 2026Dashboard downWe have identified the root cause and are putting in place mitigations to ensure this does not happen in the future.37 minResolved
May 7, 2026SCIM Database maintenence2113h 32mResolved
Apr 27, 2026Increased error rateThe issue has been resolved2h 35mResolved
Apr 26, 2026/handshake endpoint failuresThe issue has been resolved-13 minResolved
Apr 25, 2026Intermittent Issues with Development ServicesDevelopment services are back to normal.6h 52mResolved
Apr 24, 2026Clerk Services Maintenance2433h 16mResolved
Apr 24, 2026Clerk Production Services Maintenance2437h 21mResolved
Apr 23, 2026Partial Outage on Platform API All Platform API functionality has been fully restored.-1569 minResolved
Apr 8, 2026Satellite domain failuresThe incident has resolved.23 minResolved
Mar 23, 2026Degraded perfomance in webhooksWebhook delivery is operational, and the delays caused by a temporary performance degradation have been resolved.27 minResolved
Mar 20, 2026Degraded performanceThe root cause was a DDoS attack against our infrastructure. It has been fully mitigated and all systems are back to normal.53 minResolved
Mar 11, 2026JWT Templates increased 422 errorsThe root cause was identified and the issue was resolved at 20:24:10 UTC.9 minResolved
Mar 11, 2026Account Portal Degraded StateThe issue has been resolved - we're still investigating the root cause and will post more details once we have them.-125 minResolved
Mar 10, 2026Increased latency & 500 Errors on FAPI/BAPIThis incident is now resolved. We've identified the root cause and are preparing a detailed post-mortem, which we'll share soon. Thank you for your patience.1h 23mResolved
Mar 6, 2026Development instances are downA configuration was changed, and [accounts.dev](http://accounts.dev "accounts.dev") is resolving correctly again! We're continuing to monitor if there are any anomalous traffic or behavior.51 minResolved
Feb 19, 2026Full OutageWe've observed stable operations and are marking this incident as resolved2h 14mResolved
Feb 10, 2026DNS Outage causing critical services to go downA post-mortem has been published on Clerk's blog. See the write up above for details.2h 7mResolved
Feb 9, 2026GitHub.com Services Degraded Affecting OAuth Sign In22 minResolved
Feb 4, 2026Apple email address deliverability issues121h 7mResolved
Dec 19, 2025Elevated sign-in errors34 minResolved
Dec 11, 2025Organization memberships in Backend APIs and dashboard affected-7 minResolved
Dec 5, 2025Service issues24 minResolved
Dec 2, 2025Go Live is degraded due to SSL issuance delays23 minResolved
Nov 24, 2025Elevated latency and errors on authentication-15 minResolved
Nov 18, 2025Failures in CAPTCHA resolution, M2M authentication and Production Deployments4h 2mResolved
Oct 31, 2025Issues deploying to production1h 26mResolved
Oct 20, 2025Clerk Dashboard is down6h 4mResolved
Oct 11, 2025Sign in failures impacting a subset of applications-718 minResolved
Sep 29, 2025Database connectivity issues4h 48mResolved
Sep 29, 2025Issues deploying to production33 minResolved
Sep 15, 2025Performance Degradation10h 49mResolved
Sep 14, 2025Issues deploying to production18h 24mResolved
Sep 12, 2025Issues deploying to production4h 11mResolved

How to Read This Clerk Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Clerk acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Clerk outage in this window ran 101d 13h, against a mean recovery of 8d 3h. If you depend on Clerk in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.