Small percentage of deployments experiencing outage

What to do

• Check whether you use Convex Free & Starter, Free & Starter, Professional, Business and 2 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 43m it lasted.

  Anything that failed between 2026-04-09 05:42 UTC and 2026-04-09 06:24 UTC may need a replay.

• Subscribe to Convex's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=convex works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Convex 3

1. investigatingApr 9, 2026, 5:42 AM UTC

   Seems related to a problematic database failover. Updates soon.

   provider

2. monitoringApr 9, 2026, 5:59 AM UTC

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

   provider

3. resolvedApr 9, 2026, 6: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.