Status updated

All Systems Operational
Clerk logo

Clerk down?

Clerk is a user authentication and management platform for developers. It provides drop-in UI components and APIs for sign-up, sign-in, multi-factor authentication, social logins, passkeys, magic links and user profile management, with strong support for React, Next.js and modern JavaScript frameworks. Clerk also offers organisation and multi-tenant management, role-based permissions, session management, bot protection and billing features for B2B SaaS. Developers use Clerk to add secure, polished authentication to their applications in minutes.

Clerk status preview image

I have a problem with Clerk

Select the type of problem you're facing to help us and other users.

Recent User Report Trends for Clerk

Aggregated reports in the last 48 hours.

No user reports about Clerk in the last 48 hours.

uptimecard

View live report trends

Add your report to help, or tap to skip

What is Clerk's current status?

All systems are operational

No active incidents reported.

Incident history: past 7 days

times in UTC

Today

No incidents reported.

Yesterday

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 28, 2026

No incidents reported.

Oct 27, 2026

No incidents reported.

Oct 26, 2026

No incidents reported.

User Reports for Clerk

Recent issues reported by users from around the world.

No user reports for Clerk in the last 30 days.

Experiencing an issue? Add your report:

Stop refreshing this page

We'll email you the moment Clerk goes down — and again when it's back.

About Clerk & Technical Insights

What this service does and the technologies behind it.

Loading tech map…
Read the tech stack as text▾

Overview: A developer-first SaaS stack that pairs interactive code documentation and Vercel performance monitoring with accessible React UI primitives and broad multi-channel ad conversion tracking.

What stands out

  • Monaco Editor signals Clerk treats documentation as an interactive product surface, letting developers test auth flows directly in-browser.
  • Vercel Speed Insights and Vercel hosting indicate a performance-obsessed Next.js stack aligned with developer expectations.
  • Radix UI and HeroUI point to a component library strategy where Clerk's auth UI is both accessible and customizable.
  • The ad-tech mix spans Google, Reddit, Twitter, LinkedIn, and Floodlight, suggesting a diversified paid acquisition engine for subscription growth.

Technologies clerk.com uses

  • Tailwind CSS — Utility-first CSS framework styles Clerk's marketing site and dashboard, enabling rapid consistent design at scale.
  • Vercel — Hosts and deploys Clerk's Next.js marketing and docs site, giving global CDN, previews, and fast release cycles.
  • Linkedin Insight Tag — Tracks LinkedIn campaign conversions for B2B targeting.
  • Google Ads Conversion Tracking — Measures signup and subscription conversions from Google Ads, tying ad spend to Clerk's subscription revenue.
  • React — Powers Clerk's React-based UI and docs.
  • Google Ads — Runs paid search campaigns for high-intent auth and billing keywords, capturing developers comparing SaaS solutions.
  • Twitter Ads — Twitter/X ad tracking reaches developer and startup audiences, supporting Clerk's paid social acquisition mix.
  • DoubleClick Floodlight — Google Marketing Platform conversion tag tracks paid campaign performance, likely for enterprise and developer ad attribution.
  • HeroUI — Modern React UI library likely styles Clerk's marketing site and components, speeding polished pages with Tailwind-based theming.
  • Google Analytics — Measures site traffic and product funnel.
  • Vercel Speed Insights — Real-user Core Web Vitals monitoring for Clerk's Vercel-hosted marketing and docs, proving performance to developer buyers.
  • Radix UI — Provides accessible unstyled primitives behind Clerk's dashboard and embeddable UI, critical for auth components used across many apps.
  • Monaco Editor — Powers interactive code snippets and API playground in Clerk's docs, letting developers test auth flows without leaving the page.
  • Google Tag Manager — Central tag deployment for marketing and analytics.
  • Reddit Ads — Reddit ad pixel retargets developer audiences, reflecting Clerk's community-led growth in developer tooling.
  • HSTS — Enforces HTTPS for auth-related traffic.

How these technologies work together

  • Vercel runs on Vercel Speed Insights — Speed Insights runs natively on Vercel, giving Clerk real-user metrics for its Next.js marketing and docs pages.
  • Google Ads requires Google Ads Conversion Tracking — Conversion tracking cannot function without Google Ads campaigns, closing the loop from click to Clerk signup.
  • Google Analytics integrates with Google Tag Manager — Google Tag Manager deploys Google Analytics and other tags, letting Clerk manage measurement without code deploys.
  • Radix UI works alongside Tailwind CSS — Radix provides accessible behavior while Tailwind styles Clerk's UI components, a common headless plus utility pairing.
  • HeroUI requires Tailwind CSS — HeroUI components depend on Tailwind CSS, likely styling Clerk's marketing pages with consistent design tokens.
  • Monaco Editor integrates with React — Monaco editor is embedded as a React component to power editable code samples in Clerk's developer documentation.
  • React runs on Vercel — Vercel hosts Clerk's React-based site, providing optimized builds and edge delivery for developer-facing pages.
  • Google Ads integrates with Google Tag Manager — Google Ads conversion tags are fired through Tag Manager, centralizing paid acquisition measurement for Clerk.
  • Radix UI works alongside React — Radix UI is built for React, letting Clerk compose accessible auth components directly in its frontend.
  • DoubleClick Floodlight overlaps with Google Ads Conversion Tracking — Both track Google ad conversions, risking duplicate attribution and inflated numbers if not carefully configured.
  • DoubleClick Floodlight integrates with Google Tag Manager — Floodlight tags can be deployed via Tag Manager, unifying Google ad conversion tracking across Clerk's campaigns.
  • Reddit Ads works alongside Twitter Ads — Reddit and Twitter ad pixels both retarget developer audiences, complementing Clerk's paid social acquisition channels.
  • Linkedin Insight Tag works alongside Twitter Ads — LinkedIn and Twitter pixels both support Clerk's paid social targeting, though LinkedIn better fits its business-services audience.
  • HeroUI works alongside Radix UI — HeroUI and Radix both supply React UI primitives, giving Clerk's teams accessible building blocks with variant styling.
Analytics
Google AnalyticsGoogle Analytics
Vercel Speed InsightsVercel Speed Insights
Google Ads Conversion TrackingGoogle Ads Conversion Tracking
Google Tag ManagerGoogle Tag Manager
Linkedin Insight TagLinkedin Insight Tag
Business & Marketing
Reddit AdsReddit Ads
Twitter AdsTwitter Ads
Google AdsGoogle Ads
DoubleClick FloodlightDoubleClick Floodlight
Content
Monaco EditorMonaco Editor
Servers
VercelVercel
Web Development
Tailwind CSSTailwind CSS
Radix UIRadix UI
HSTSHSTS
HeroUIHeroUI
ReactReact

Trust & Safety Checks

Public registration, DNS and certificate records UptimeCard checked independently for the domain clerk.com.

Domain name active since 1996

clerk.com has been a registered domain since April 1996 — 30 years at the same web address.

Domain lock enabled

The registry blocks unauthorised transfers, deletion and record changes, so the domain cannot be hijacked.

Registered through 2033

The owner has kept this domain secured until April 2033.

DNS managed by DNSimple

7 nameservers answer for this domain, so it stays reachable even if one goes offline.

Hosted by Amazon.com, Inc.

Served from professional infrastructure located in United States.

Records last verified September 2026.

How to fix Clerk not working

Clerk provides sign-up, sign-in and user management for apps, with ready-made components and APIs. Developers add it to their apps, and their own users sign in through it. Find your symptom below. Most problems come from a sign-in setting, a key that does not match the environment, a connected service, or the platform itself. Never share secret keys in a support message.

Jump to what you are seeing

Website

The Clerk website does not load for you.

  1. Open the page in a private window and on another network.
  2. Check status.clerk.com for an active incident.
  3. If only your network is affected, ask IT to check the firewall.

Login

Users cannot sign in or sign up through the app's Clerk screens.

  1. Check the publishable key matches the environment, and that the sign-in method you turned on is enabled.
  2. Check the user's email is verified, and that their verification code has not expired.
  3. Check status.clerk.com, and test with a new user in a private window.

Integrations

A connected service, such as a webhook or a third-party provider, stops receiving user events.

  1. Check the endpoint address is reachable, and returns a success response.
  2. Check the signing secret for the webhook matches the one in the dashboard.
  3. Check status.clerk.com, then send one test event before you rely on it.

Still not working?

Contact your developer, or the person who manages your Clerk account, first. For a platform-wide problem, contact Clerk support through the help option in the dashboard or on the Clerk website. Have your application name, the environment, the exact error text, the user or event ID (not their personal details), and the time with your time zone. Never send secret keys, passwords or session tokens in a support message. Live incident updates are on status.clerk.com.

Most sign-in problems come from a key or environment mismatch, a setting that is off or an unverified email, and they usually clear once that is checked. The status page shows live incidents, so you can see whether the problem is on Clerk's side.

Frequently asked questions about Clerk

Is Clerk down right now?

No. Based on the latest status data on this page, Clerk (clerk.com) is up and running normally. The most recent incident, "SMS delivery issues affecting verification codes", was resolved (last update Oct 29, 2026).

What should I do if Clerk is not working for me?

First rule out your side: reload the page, try another browser or device, clear the cache and cookies for clerk.com, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.

What was the most recent Clerk incident?

The most recent incident on record is "SMS delivery issues affecting verification codes", last updated on Oct 29, 2026. It has been resolved.

How many people reported problems with Clerk recently?

No user reports about Clerk were submitted in the last 48 hours.

How do I report a problem with Clerk?

Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.

Where is the official Clerk status page?

The official status page for Clerk is status.clerk.com.

Related Keywords

Common themes, topics and technologies associated with clerk.com.

authenticationuser managementclerk authnext.js authenticationreact authuser profilessocial loginoauth providerpasswordless loginmagic linksmulti-factor authenticationmfa2fasession managementsaas authenticationb2b authmulti-tenancyorganization managementrole based access controlrbacdeveloper authauth componentslogin uisignup flowidentity provideridpjwt authenticationclerk sdkuser onboardingmanaged auth serviceweb securityfrontend authenticationbackend authenticationserverless authtypescript authauth for remixauth for redwoodjsuser dashboarddeveloper experiencecloud authentication