Who is down right now

26 down now · 292 this week

Convex · Data and observabilityApr 9, 2026, 05:42 UTC 7 months ago

Small percentage of deployments experiencing outage

MajorDatabaseUpdated 49d ago
Apr 9, 05:42 UTCApr 9, 06:24 UTC
Duration
43m
Impact
Major
Root cause
Database
Convex, 90 days
4 incidents
Affected
Free & StarterProfessionalBusinessLive Traffic - Free & StarterLive Traffic - ProfessionalLive Traffic - BusinessDevelopment Services - Free & StarterDevelopment Services - ProfessionalDevelopment Services - Business
Status page

Final update

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.

Timeline

  1. Resolved · Apr 9, 06:24 UTC
    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.
  2. Monitoring · Apr 9, 05:59 UTC
    A fix has been implemented and we are monitoring the results.
  3. Investigating · Apr 9, 05:42 UTC
    Seems related to a problematic database failover. Updates soon.

More from Convex

Full history

Also caused by database

All