- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Convex. 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 0m it lasted.
Anything that failed between 2026-01-27 04:43 UTC and 2026-01-27 04:30 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 1
- resolved
A configuration change in our function runner service caused error rates to increase across all Convex deployments between 8:20pm PT and 8:35pm PT. This change has been rolled back, and all deployments should be operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c8b80f3837
Is Convex still down?
No, this incident was resolved 2026-01-27 04:30 UTC. For Convex's live state, see https://down.guide/convex.
How long did it last?
0m, from 2026-01-27 04:43 UTC to 2026-01-27 04:30 UTC, by the times Convex posted.
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.