← Back to the carnage
CONVEX
🟠 AWS's availability zone threw a tantrum and took Convex's infrastructure hostage for a bit. They've since evacuated to safer ground, but the patient's still in recovery—monitoring for any lingering fever from the AWS mess. (Auto-resolved: no updates in 24h)
// The official story
Intermittent Impact from AWS Outage
// Status page says
May 8 , 01:51 UTC Monitoring - We’ve moved affected infrastructure out of the impacted AWS Availability Zone, and traffic should now be restored. We’re continuing to monitor for any residual impact while AWS’s recovery progresses. May 8 , 00:54 UTC Update - AWS’s Availability Zone-level issue is continuing to cause impact to our infrastructure. Some customers may experie
🔗 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)