Convex had 43 outages in the last 2 years totaling 36h 32m of downtime — averaging 1.8 incidents per month.
There were 43 Convex outages since May 21, 2025 totaling 36h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
Identified an issue. Remediating. Pro customers have been remediated fully. Continuing to monitor
This incident has been resolved.
Our upstream authentication provider is affected by the AWS us-east-1 outage. This is currently impacting the ability for Convex users to login to the Convex dashboard and command line to manage projects. This does not affect your backend traffic.
We are continuing to investigate this issue.
This incident has been resolved.
We're seeing note action availability problems due to AWS Lambda issues.
Issue should be resolved. Monitoring to ensure things are working.
This incident has been resolved.
Usage information can't be queried at the moment; we believe this is caused by a new round of AWS issues.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Many databases are currently broken due to an AWS outage in us-east-1
AWS has mitigated the issue and services are recovering.
This incident has been resolved.
Project creation and the dashboard are currently down
Project management was unavailable for approximately 15 mins after a database cluster was removed from circulation following a series of upgrades we're performing. Projects were otherwise running and serving traffic successfully during this period.
A bug in our downstream infrastructure provider caused a database cluster to deadlock when it was being resized.
We are currently investigating this issue.
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.
This incident has been resolved.
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.
We're experiencing sporadic connection drops in Convex's project management service that may require retries to deploy projects, load the dashboard, etc.
This incident has been resolved.
We're performing some maintenance on our databases that will result in a brief period of unavailability for some users.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're performing some maintenance on our databases that will result in a brief period of unavailability for non-pro instances. Pro instances may see degraded performance briefly.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We're performing a database upgrade that is impacting availability for a small subset of non-pro Convex instances.
This incident has been resolved.
We're investigating reports that some instances are still unavailable following the downtime earlier today.
We've identified an issue affecting a different database. We're working on failing over this database and restoring service to affected instances.
The second database issue has been resolved and all Convex instances are back online.
A database outage is affecting a portion of Convex deployments. We have identified the issue and are working on restoring full functionality.
The database was failed over successfully and traffic is being incrementally restored. Pro customers should be fully functional, and we we expect full resolution for all other customers by 15:50 UTC.
This incident has been resolved. All Convex instances are fully operational at this time.
A small portion of Convex backends are intermittently unavailable. We've identified the cause and are working towards resolution.
All Convex backends are now available. This incident is resolved.
We are currently investigating this issue.
We have found the issue causing intermittent unavailability for a portion of Convex instances, and are monitoring recovery.
This incident has been resolved.
We are currently investigating this issue.
Incident appears to be out-of-memory conditions in our traffic layer. Tentativey marking recovered, but team is still monitoring.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
The Convex dashboard is currently down and we are in the process of restoring access. Backends, code pushes and project creation should be unaffected.
This incident was a result of some internal traffic routing maintenance that had a larger impact than expected.