Minor impactResolvedDatabases

Convex incident: elevated latency/errors for a subset of customers

Convex reported this minor-impact incident on its official status page on Oct 31, 2025, 14:25 UTC. It was resolved after 47 min.

Right now Convex is operational. Live Convex status →

🔔 Get alerted when Convex has issuesFree · email alerts · no credit card

Oct 31, 2025, 14:25 UTC

started

Oct 31, 2025, 15:12 UTC

resolved

47 min

duration

Minor

impact

Affected components

Free & Starter

Timeline

updates from Convex's status page ↗

resolvedOct 31, 2025, 15:12 UTC
This incident has been resolved.
identifiedOct 31, 2025, 14:51 UTC
Brought back pro deployments. Continuing to work on free
identifiedOct 31, 2025, 14:25 UTC
An issue is identified affecting a subset of deployments.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Convex's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

Mux: Investigating elevated playback errors on Chrome version 141.0.7390.123 and laterMinor · Oct 23, 2025, 14:16 UTC

How often does Convex have incidents?

Convex reported 5 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 57 min. See Convex's uptime and incident history

← Previous: elevated latency/errors for a subset of customers (Oct 30, 2025)Next: elevated latency/errors for a subset of customers (Nov 3, 2025) →