All Systems Operational

Uptime over the past 90 days. View historical uptime.
Live Traffic Operational
90 days ago
99.93 % uptime
Today
Free & Starter Operational
90 days ago
99.93 % uptime
Today
Professional Operational
90 days ago
99.98 % uptime
Today
Business Operational
90 days ago
99.98 % uptime
Today
Development Services Operational
90 days ago
99.92 % uptime
Today
Free & Starter Operational
90 days ago
99.92 % uptime
Today
Professional Operational
90 days ago
99.9 % uptime
Today
Business Operational
90 days ago
99.9 % uptime
Today
convex.dev website Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Apr 23, 2026

No incidents reported today.

Apr 22, 2026

No incidents reported.

Apr 21, 2026
Login/Deployment/Dashboard services impacted
Resolved - Login/Deployment/Dashboard services are confirmed restored
Apr 21, 16:56 UTC
Update - We are continuing to monitor for any further issues.
Apr 21, 16:41 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 21, 16:41 UTC
Investigating - Load issues are affecting our authentication, dashboard, and project deployment services.

Your application live traffic is unaffected.
Apr 21, 16:04 UTC
Apr 20, 2026

No incidents reported.

Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026

No incidents reported.

Apr 16, 2026

No incidents reported.

Apr 15, 2026

No incidents reported.

Apr 14, 2026

No incidents reported.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

No incidents reported.

Apr 9, 2026
Small percentage of deployments experiencing outage
Resolved - This issue is considered resolved.

Impact: A small percentage of Convex deployments experienced sporadic availability for approximately 17 minutes, from 22:42 to 22:59 PM PT.

Root cause: one of our database clusters experienced a routine primary failover event. During the primary promotion process, the orchestration system failed to provision a replica that was ready to accept new database writes.

Out of an abundance of caution, Convex will only use database clusters that support semi-sync replication, where at least two machines persist the writes before considering the write successful.

Since the replicas were not ready, this cluster was not usable by Convex. Human operators were paged to intervene and fix the broken automation. We're working with our database partners to better understand what went wrong and what changes will prevent it in the future.
Apr 9, 06:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 9, 05:59 UTC
Investigating - Seems related to a problematic database failover. Updates soon.
Apr 9, 05:42 UTC
← Incident History Powered by Atlassian Statuspage