Convex Status: How to Check If Convex Is Down (2026)
Updated June 2026 · 5 min read · By API Status Check
Quick Answer: Check Convex Status Now
Convex is a reactive backend-as-a-service that combines a document database, serverless functions (queries, mutations, and actions), real-time subscriptions, and file storage in a single TypeScript-native platform. When Convex goes down, apps that rely on its real-time useQuery hooks stop receiving live updates, mutations fail, and scheduled functions may be skipped. This guide explains how to check Convex's status and distinguish a platform outage from a deployment configuration issue.
Understanding Convex's Status Page (status.convex.dev)
Convex operates status.convex.dev — its official status page. Convex runs deployments on AWS infrastructure with per-deployment isolation, meaning a platform incident can affect all deployments simultaneously, or issues may be isolated to specific AWS regions or individual deployment environments.
Convex Platform
Core function execution — queries, mutations, and actions running in your Convex deployment. Platform incidents directly affect all real-time subscriptions and write operations. This is the most critical component for application functionality.
Convex Database
The document database storing your application data. Database incidents affect read and write operations. Convex uses ACID transactions with full consistency guarantees — a database incident means queries return errors rather than stale or inconsistent data.
Convex Dashboard
dashboard.convex.dev — the web console for viewing data, monitoring function logs, managing schedules, and inspecting deployments. Dashboard incidents prevent browser-based management but don't affect your application's function execution.
Convex API / CLI
The management API used by `npx convex dev`, `npx convex deploy`, and the Convex CLI. API incidents block schema pushes and deployments but typically don't affect running production deployments.
What Convex Status Colors Mean
⚠️ Convex Platform Issue vs. Deployment Issue — Know the Difference
Many "Convex is down" reports turn out to be deployment configuration issues, not platform outages. Before assuming a platform problem:
- Verify your
CONVEX_URLenvironment variable matches your deployment - Run
npx convex devto check for schema or function errors - Check the Convex dashboard for function execution errors in your deployment logs
- Verify you're using the correct deployment (dev vs. production)
- Check the Convex Discord #help channel for similar reports
Monitor your Convex backend with independent uptime monitoring
Convex's status page shows platform health — not your specific deployment's health. Better Stack monitors your actual Convex-powered app endpoints and alerts you when they go down. Free plan available.
Try Better Stack Free →5 Ways to Check If Convex Is Down
status.convex.dev (Official)
Convex's official status page, showing real-time status for the platform, database, and dashboard. The most reliable source for platform-wide incidents. Subscribe to email notifications to receive updates automatically.
Check status.convex.dev →Convex Dashboard Function Logs
Open dashboard.convex.dev, navigate to your deployment, and check the Function Logs. If your functions are throwing errors, you'll see them here with full stack traces. This distinguishes a platform issue from a function-level error in your own code.
Open Convex dashboard →Convex Discord
Convex maintains a very active Discord community where outage reports surface quickly. The #help and #status channels are the fastest sources for incident confirmation. The Convex team is responsive and often acknowledges issues in Discord before the official status page is updated.
Join Convex Discord →@convex_dev on X
Convex's official X account posts incident updates and maintenance announcements. The team is active during outages and provides status updates directly on X.
Follow @convex_dev →X / Twitter (Search)
Search 'convex down' or 'convex backend outage' on X. Developers using Convex in Next.js, React, and Expo apps report issues quickly on X. Searching for related terms like 'convex useQuery failing' can also surface active incidents.
Search X for 'convex down' →Common Convex Issues and What They Mean
"Could not connect to Convex backend"The Convex client can't reach your deployment. Check your CONVEX_URL environment variable — it should look like `https://<deployment-name>.convex.cloud`. Verify the deployment exists in your Convex dashboard. This error can also appear if the Convex platform is down."Convex function timed out"Your query, mutation, or action exceeded Convex's execution time limit. Queries and mutations have a shorter timeout (~30s), while actions support longer execution. For long-running tasks, break work into smaller mutations or use actions with explicit chunking."Schema validation error"A mutation tried to write data that doesn't match your schema definition. Check your `convex/schema.ts` for field types and required fields. This is a code-level error, not a platform outage."Optimistic update conflict"Your optimistic update in the client conflicted with the server result. Convex's optimistic updates are applied locally before the server confirms the mutation — conflicts are automatically rolled back to the server state. This is expected behavior, not an error."Too many requests / rate limited"Your deployment is exceeding its function call rate limits. Check the Convex pricing tier for your deployment's limits. High-frequency real-time subscriptions with many concurrent users can trigger rate limits on lower tiers."Deployment not found"The CONVEX_URL points to a deployment that no longer exists or was deleted. Check your Convex dashboard for active deployments. If you recently deleted and recreated a project, update CONVEX_URL to the new deployment URL.Convex Outage History: What the Data Shows
Convex is a newer platform (public launch 2023) that differentiates itself with a reactive architecture where queries automatically re-run when underlying data changes. Its platform runs on AWS with strong isolation between customer deployments. Most incidents affect function execution latency or throughput rather than complete unavailability. The Convex team is active in its Discord community during incidents and typically provides timely status updates. Because Convex combines database and compute in one platform, incidents tend to affect both layers simultaneously rather than independently.
What to Do When Convex Is Down
If Queries / Mutations Are Failing
- Check status.convex.dev for platform incidents
- Check dashboard function logs for error details
- Verify CONVEX_URL is correct in your environment
- Run
npx convex devto diagnose locally - Search Convex Discord for active reports
For Better Outage Resilience
- Use optimistic updates for mutation feedback
- Implement error boundaries around Convex-dependent UI
- Cache critical data client-side with SWR or React Query as fallback
- Show loading/error states rather than blank screens
- Set up independent endpoint monitoring for your app
Frequently Asked Questions
Where is the official Convex status page?
Convex's official status page is at status.convex.dev. It shows real-time status for the Convex platform, database, and dashboard. Subscribe to email notifications to receive alerts when incidents are posted and resolved.
My Convex useQuery hook stopped updating but the status page is green — what's wrong?
When useQuery stops delivering updates but the status page is green, the issue is typically in your deployment or network. Check the Convex dashboard for function execution errors in your deployment. Verify your CONVEX_URL environment variable matches your production deployment. In some cases, a WebSocket connection issue between the client and Convex can cause subscriptions to stop without a full platform outage — reload the page to force reconnection.
What happens to Convex scheduled functions during an outage?
During a Convex platform outage, scheduled functions (crons and one-off schedules) that were due to run will be delayed or missed. Convex does not guarantee that missed scheduled runs are retried after an outage — it depends on the nature and duration of the incident. After an outage, check the Convex dashboard's Schedules section to review which scheduled functions ran and which were missed.
Can I use Convex with Next.js App Router and Server Components?
Yes — Convex supports Next.js App Router. For Server Components, use the Convex HTTP API or preloaded queries with `preloadQuery`. For Client Components, use `useQuery` and `useMutation` from `convex/react`. Real-time subscriptions (useQuery) only work in Client Components. During a Convex outage, Server Component data fetching will fail at request time rather than failing silently.
How do I monitor my Convex-powered app uptime independently?
Add a health check API route to your application that calls a Convex query (e.g., a simple `ctx.db.query('users').first()`) and returns HTTP 200 if successful. Monitor that endpoint with Better Stack or API Status Check Alert Pro. This catches Convex connection issues that aren't reflected in the platform status page, including deployment-specific problems.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Convex goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Convex + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial