← Back to the carnage
CONVEX
🟡 Someone else's server caught fire and Convex customers are feeling the heat. Jobs are being shuffled around like deck chairs on the Titanic while databases attempt their best impression of a functioning system. Apparently 'upstream' is code for 'we have no control over this.'. (Auto-resolved: no updates in 24h)
// The official story
Intermittent Impact from Upstream Infrastructure Outage
// Status page says
May 8 , 00:16 UTC Investigating - We’re experiencing intermittent downtime from an upstream infrastructure provider. Some customer workloads may see brief error spikes while affected jobs are reallocated to healthy hardware and databases fail over. We’re monitoring recovery and will provide updates as mitigation progresses.
🔗 Official status page (for the PR-approved version)
https://status.convex.dev/incidents/7ttckbkcpjgfConvex's Greatest Hits
🟢 CONVEX
3d ago
⚪ Some query and mutation executions decided to ghost their users for 41 minutes thanks to an upstream network hiccup. Convex's infrastructure had commitment issues, but they're back to pretending everything's fine now. (Auto-resolved: no updates in 24h)
🟢 CONVEX
Sep 28, 2026
🟡 Convex's AI gateway decided to become an actual gatekeeper—turns out it wasn't just a metaphorical job. The service is currently ghosting requests like a bad date, leaving engineers to frantically check their send logs. (Auto-resolved: no updates in 24h)
🟢 CONVEX
Jun 15, 2026
🟠 Convex decided to test how many errors could fit in a deployment simultaneously. Most machines failed the audit; D1024s apparently have better lawyers. Fixed faster than you can say 'why is monitoring configured like this?'. (Auto-resolved: no updates in 24h)
🟢 CONVEX
May 29, 2026
🟠 Convex's European servers decided to throw a tantrum, sprinkling errors across a subset of deployments like they're conducting a stress test nobody asked for. Engineers implemented a fix and are now nervously refreshing their monitoring dashboards. (Auto-resolved: no updates in 24h)