Clerk incident

Development instances are down

Minor Resolved View vendor source →
Started
Mar 06, 2026, 05:27 PM UTC
Resolved
Mar 06, 2026, 05:27 PM UTC
Duration
Detected by Pingoru
Mar 06, 2026, 05:27 PM UTC

Update timeline

  1. investigating Mar 06, 2026, 04:36 PM UTC

    Status: Investigating Development instances are currently down. We are investigating. We do not expect this to extend to production instances.

  2. investigating Mar 06, 2026, 04:49 PM UTC

    Status: Investigating We're continuing investigating the issue, and will post more updates soon

  3. investigating Mar 06, 2026, 04:53 PM UTC

    Status: Investigating We are investigating an issue with DNS resolution for development hosts on our accounts.dev "accounts.dev": http://accounts.dev domain. Production instances are unaffected

  4. investigating Mar 06, 2026, 05:06 PM UTC

    Status: Investigating We have made a configuration change and are monitoring for signs of recovery. Continuing to investigate the root cause.

  5. investigating Mar 06, 2026, 05:20 PM UTC

    Status: Investigating We're continuing to investigate the root cause. Working with our DNS provider to resolve the issue

  6. resolved Mar 06, 2026, 05:27 PM UTC

    Status: Resolved A configuration was changed, and accounts.dev "accounts.dev": http://accounts.dev is resolving correctly again! We're continuing to monitor if there are any anomalous traffic or behavior.

Looking to track Clerk downtime and outages?

Pingoru polls Clerk's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Clerk reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Clerk alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Clerk for free

5 free monitors · No credit card required