Convex reported this major-impact incident on its official status page on Sep 20, 2025, 12:18 UTC. It was resolved after 57 min.
Right now Convex is operational. Live Convex status →
From around 5:18am to 5:54am Pacific \(12:18pm to 12:54pm UTC\), Convex had a 36 min period of intermittent downtime that affected all Convex services. The specific issue was a cascading failure in our traffic layer. We had a traffic node \(Caddy\) run out of memory due to an unforeseen load spike and instead of just being restarted/replaced this node was marked as permanently down by our container management layer \(Nomad\) which led to the issue propagating to all traffic servers. Since the incident we've more than doubled the size of our traffic layer, fixed the failover behavior which led to nodes staying failed after OOMing, and will be investigating alternative traffic services. As always data was safe during this incident but we really apologize for the availability impact during that time period.
This incident has been resolved.
An unexpected traffic pattern overloaded some of our services, causing intermittent unavailability across Convex instances. We've added extra capacity and are monitoring to ensure that the system is stable.
We are currently investigating this issue.
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.
Overlapping incidents aren't necessarily related.
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