Is Clerk down right now?
Real-time Clerk status from status.clerk.com. Clerk provides drop-in auth for React/Next.js apps. We track the Frontend API, Backend API, dashboard, and webhooks.
Major outage: AWS
Clerk
OperationalDrop-in auth + user management for React.
Status from status.clerk.com · last fetched 12s ago
Developer Platforms
Upstream returned 404
Atlassian source hosting and Pipelines.
Container image registry and Docker Desktop.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
Some users unable to sign up with Apple on the Claude iOS app — started 1 day ago
Delayed Costs Data in the Compliance API — started 2 days ago
Upstream returned invalid JSON
Upstream returned invalid JSON
AI code editor — chat, tab, composer.
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
Cloud / Hosting
Service disruption: Increased Error Rates — started 61 days ago
Changes to Cloudflare Workers are not producing Event Subscription events — started 5 days ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Global app servers, Postgres, volumes.
Compute, Storage, BigQuery, Cloud Run.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Next.js hosting, Edge, Serverless functions.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 — started 73 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
SMS Delivery Receipt Failures from Twilio to Claro Costa Rica — started 3 days ago
SMS Delivery Receipt Failures from Twilio to Claro Costa Rica — started 3 days ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Auth / Identity
Communication
Monitoring / Dev Tools
Upstream returned 403
Upstream returned invalid JSON
Upstream returned invalid JSON
Collaborative design, FigJam, Dev Mode.
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
Clerk 90-day incident history
Last 90 days
90.00% incident-free
Quick facts about Clerk
- Clerk publishes status at status.clerk.com (Statuspage.io).
- Frontend API (used by sign-in components) and Backend API are reported separately.
- Webhooks are queued and replayed during outages.
Frequently asked questions
Why are my Clerk sign-ins failing with 503?
A 503 from Clerk is usually a Frontend API issue. Check the dashboard above. If green, check your publishable key and that the Clerk component’s domain is allowed in your Clerk dashboard.