Convex incident

elevated latency for a small subset of convex deployments

Notice Resolved View vendor source →

Convex experienced a notice incident on March 25, 2026, lasting 3h 19m. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2026, 04:27 PM UTC
Resolved
Mar 25, 2026, 07:46 PM UTC
Duration
3h 19m
Detected by Pingoru
Mar 25, 2026, 04:27 PM UTC

Update timeline

  1. investigating Mar 25, 2026, 04:27 PM UTC

    We're investigating elevated latency for functions on a subset of Convex deployments

  2. identified Mar 25, 2026, 05:54 PM UTC

    A small subset of free instances are experiencing availability issues while we restore service.

  3. resolved Mar 25, 2026, 07:46 PM UTC

    This incident has been resolved.

  4. postmortem Mar 25, 2026, 07:47 PM UTC

    We had elevated latencies on a single database that required us to temporarily shed load while resizing and reparenting the db. This lead to a period of elevated latencies for all instances on that database followed by downtime for a smaller subset of instances while we performed the maintenance operation. This issue should not occur under normal circumstances and was due an underlying database problem that required manual intervention to resolve. We apologize for the impact to those impacted!