BREAKING: Clerk MINOR — Elevated Error Rate in Domain Provisioning [01KYW237CJ2GE1F3VVZ5A0H0B5]

Clerk experiencing partial disruption in domain provisioning. Immediate workarounds and monitoring guidance for indie hackers.

BREAKING: Clerk Domain Provisioning Outage — What You Need to Know

Status: Identified | Severity: Minor | Impact: Partial Disruption Last Updated: [Current Time]

---

What's Down

Clerk's domain provisioning service is experiencing an elevated error rate. This affects:

New domain setup for custom authentication domains

Domain verification processes for production instances

SSL certificate provisioning tied to domain creation

Who's affected: Projects attempting to add new custom domains or re-verify existing ones. Existing authentication flows remain operational.

---

Immediate Workarounds (Use NOW)

If you need a custom domain urgently:

1. Delay non-critical domain setup — If your launch isn't today, wait 2-4 hours. The issue is actively being resolved.

2. Use Clerk's default domain — Your auth endpoints work fine on *.clerk.accounts.com. Use this temporarily: ``` https://YOUR-INSTANCE.clerk.accounts.com ```

3. Pause DNS propagation �� Don't point your domain DNS to Clerk yet. Wait until we confirm recovery.

4. Check your staging environment — Some regions are unaffected. Test with a different region if available in your dashboard.

---

How to Check If You're Affected

Quick diagnostic:

1. Go to Clerk Dashboard → Domains 2. Attempt to add a new custom domain 3. If you see Error: Domain provisioning failed or timeout on verification, you're affected 4. Existing domains remain functional — this only blocks *new* provisioning

Check your auth flow:

Test login/signup on your app — should work normally

Only domain *management* operations are impacted

---

Alternative Tools to Consider

If you absolutely need a custom domain immediately:

Auth0 — Custom domain provisioning (setup takes 10-15 min)

Firebase Auth — Built-in custom domain support

Supabase Auth — Faster domain setup than Clerk currently

AWS Cognito — Custom domain via CloudFront (advanced)

Reality check: Most indie hackers can operate on Clerk's default domain for 24 hours. Consider alternatives only if this blocks a hard deadline.

---

How to Monitor Recovery

Real-time status:

Check Clerk's status page: status.clerk.com

Twitter: @ClerkHQ for updates

Dashboard banner alerts — watch for green checkmark

Verification checklist (test every 30 min):

```bash

Try provisioning a test domain

If this succeeds, you're good to go

curl -X POST https://api.clerk.com/v1/domains \ -H "Authorization: Bearer YOUR_API_KEY" \ -d '{"name": "test-domain.com"}' ```

Expected recovery timeline: 2-4 hours from incident start (identified ~15 min ago).

---

What Clerk Is Doing

Root cause isolated in domain provisioning queue

Engineering team actively deploying fix

Monitoring error rates in real-time

No data loss — existing authentication unaffected

---

Bottom Line

This is minor and temporary. Your app's auth continues working. New custom domain setup is blocked for now.

Do:

Use default Clerk domain temporarily

Monitor status.clerk.com

Test in 30-min intervals

Don't:

Panic-migrate auth providers (not necessary)

Point DNS to Clerk until confirmed working

Contact Clerk support (they know — this is identified)

We'll update this post as recovery completes. Check back in 2 hours for all-clear.

—*Senior Dev, StillNotAThing*