elevated error rates on convex for pro instances

What to do

• Check whether you use Convex Free & Starter. 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 38m it lasted.

  Anything that failed between 2026-03-12 13:17 UTC and 2026-03-12 13:55 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 4

1. investigatingMar 12, 2026, 1:17 PM UTC

   We are currently investigating an issue leading to higher error rates

   provider

2. monitoringMar 12, 2026, 1:40 PM UTC

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

   provider

3. resolvedMar 12, 2026, 1:55 PM UTC

   This incident has been resolved.

   provider

4. postmortemMar 13, 2026, 3:36 AM UTC

   At approximately 6am Pacific we had a high rate of server errors for approximately 30 minutes for a subset of customer backends. This was caused by a 20x increase in traffic that saturated one of our databases and led to resource exhaustion on one of our function execution clusters, which is why the impact spilled beyond just that specific database. We’ve scaled up our infrastructure further and are deploying some changes to load shedding and retries to minimize the impact of such an event in future. While we aim to have no cascading impact on other customers from a load spike we’re also deploying dedicated isolated hardware for customers on our upcoming Business plan.

   provider

Corrections

None so far.

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