Convex incident

Small percentage of deployments experiencing outage

Resolved after 42 minutes, affecting Free & Starter and Free & Starter and 1 more, on April 9, 2026.

resolved Apr 09, 2026, 06:24 AM 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.

Started
Apr 09, 2026, 05:42 AM UTC
Resolved
Apr 09, 2026, 06:24 AM UTC
Duration
42m
Detected by Pingoru
Apr 09, 2026, 05:42 AM UTC

Affected components

Free & StarterFree & StarterProfessionalBusinessProfessionalBusiness

Update timeline

  1. investigating Apr 09, 2026, 05:42 AM UTC

    Seems related to a problematic database failover. Updates soon.

  2. monitoring Apr 09, 2026, 05:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 09, 2026, 06:24 AM 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.

Your product runs on more than Convex

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →