Convex: elevated latency/errors for a subset of customers

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 2h 12m it lasted.
Anything that failed between 2025-10-28 21:38 UTC and 2025-10-28 23:50 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.

investigatingOct 28, 2025, 9:38 PM UTC
We're investigating an issue with a database cluster leading to degraded performance and higher error rates for affected deployments.
provider
identifiedOct 28, 2025, 9:50 PM UTC
Service has been restored to Pro customers and we're working on restoring free deployments.
provider
resolvedOct 28, 2025, 11:50 PM UTC
This incident has been resolved. The specific cause was due to a maintenance operation from a downstream provider which resulted in a database cluster switching to using an unoptimized table format. We'll be working to ensure the underlying cause is resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Convex still down?

No, this incident was resolved 2025-10-28 23:50 UTC. For Convex's live state, see https://down.guide/convex.

How long did it last?

2h 12m, from 2025-10-28 21:38 UTC to 2025-10-28 23:50 UTC, by the times Convex posted.

What was affected?

Convex named Free & Starter.

What caused it?

Convex hasn't published a root cause. If it does, it shows here.

Where does this come from?

Convex's official status page, https://status.convex.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.