Convex had 43 outages in the last 2 years totaling 26h 13m of downtime — averaging 1.8 incidents per month.
There were 43 Convex outages since May 21, 2025 totaling 26h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
A configuration update caused an unintended restart of many Convex deployments, resulting in intermittent unavailability from 00:52 to 00:54 UTC in the US East region and from 01:05 to 01:07 UTC in the EU West region. Service has since returned to normal.
We are currently investigating.
A fix has been implemented. Monitoring to ensure error rates are down on all affected deployments
This incident has been resolved.
We’ve identified an issue causing newly configured custom domains to remain in the pending verification state. Existing custom domains continue to function normally. We’re working with our upstream provider to resolve the issue and will provide updates as we have more information.
This incident has been resolved.
The team has identified the issue and is reverting the change. We'll update on status as we resolve for the affected Convex customers.
A mitigation has been rolled out for all users on pro plans. It will be rolled out to all users on Free and Starter plans soon. Please redeploy your projects with `npx convex dev` and `npx convex deploy` and your HTTP actions should begin working immediately. We'll also roll out a fix soon that does this automatically if you don't get to it first.
We've reverted 100% of deployments, and a code deployment will resolve HTTP action issues. We'll wait to resolve this incident until we've automatically fixed the few remaining deployments with HTTP action issues that developers have not pushed code for.
All deployments have been automatically repaired, and HTTP actions are working across the entirety of Convex's cloud. Our team will follow up with a postmortem soon.
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.
AWS has identified an Availability Zone-level issue affecting our infrastructure. Some customer workloads may continue to experience intermittent errors while affected jobs are reallocated to healthy hardware and databases fail over. We’re continuing to monitor recovery and will provide updates as AWS mitigation progresses.
AWS’s Availability Zone-level issue is continuing to cause impact to our infrastructure. Some customers may experience extended downtime or elevated error rates while affected workloads recover on healthy infrastructure. We’re actively working to restore service for impacted customers and will continue to provide updates as recovery progresses.
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.
We’ve mitigated the impact from AWS’s Availability Zone issue, and service has remained stable. We have not observed further node failures or customer impact, so we’re marking this incident as resolved. We’ll continue to monitor AWS’s recovery separately.
Convex on-call engineers are investigated elevated latency for function calls on a small set of Convex deployments
A fix has been implemented and we are monitoring the results
This incident has been resolved.
Database issue affecting our authentication, dashboard, and project deployment services. Your application live traffic is unaffected.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
Login/Deployment/Dashboard services are confirmed restored
Seems related to a problematic database failover. Updates soon.
A fix has been implemented and we are monitoring the results.
This issue is considered resolved. Impact: A small percentage of Convex deployments experienced sporadic availability for approximately 17 minutes, from 22:42 to 22:59 PM PT. Root cause: one of our database clusters experienced a routine primary failover event. During the primary promotion process, the orchestration system failed to provision a replica that was ready to accept new database writes. Out of an abundance of caution, Convex will only use database clusters that support semi-sync replication, where at least two machines persist the writes before considering the write successful. Since the replicas were not ready, this cluster was not usable by Convex. Human operators were paged to intervene and fix the broken automation. We're working with our database partners to better understand what went wrong and what changes will prevent it in the future.
An unplanned database promotion has caused some deployments to become unavailable. We're investigating now.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating elevated latency for functions on a subset of Convex deployments
A small subset of free instances are experiencing availability issues while we restore service.
This incident has been resolved.
We had elevated latencies on a single database that required us to temporarily shed load while resizing and reparenting the db. This lead to a period of elevated latencies for all instances on that database followed by downtime for a smaller subset of instances while we performed the maintenance operation. This issue should not occur under normal circumstances and was due an underlying database problem that required manual intervention to resolve. We apologize for the impact to those impacted!
Provisioning new backends is currently limited and will be resolved shortly
Service is being restored
This incident has been resolved.
We are currently investigating an issue leading to higher error rates
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At approximately 6am Pacific we had a high rate of server errors for approximately 30 minutes for a subset of customer backends. This was caused by a 20x increase in traffic that saturated one of our databases and led to resource exhaustion on one of our function execution clusters, which is why the impact spilled beyond just that specific database. We’ve scaled up our infrastructure further and are deploying some changes to load shedding and retries to minimize the impact of such an event in future. While we aim to have no cascading impact on other customers from a load spike we’re also deploying dedicated isolated hardware for customers on our upcoming Business plan.
A small subset of customers are currently experiencing downtime while we reprovision some hosts. We are working on restoring service.
This incident has been resolved.
A misconfiguration caused many custom domains to stop working with a TLS error. We are rolling out a fix.
All hostnames have been reconfigured and should be available again.
This incident has been resolved.
We’ve identified an overloaded database that’s causing intermittent errors in parts of the Convex Dashboard and CLI. Live traffic to Convex deployments is unaffected. We’re scaling the affected database now and will share another update shortly.
Error rates are back to baseline. We’re monitoring for stability, but the incident appears resolved.
This incident has been resolved.
We've identified an issue temporarily blocking redirects for authentication on some non-pro instances. We're actively working on a fix and expect to have this resolved soon.
This incident has been resolved.
Some customers are currently unable to push new code without hitting an OptimisticConcurrencyControlFailure error. We're investigating and working on resolving.
We've identified a fix and are rolling it out to a subset of customers before deploying more widely
This incident has been resolved.
A configuration change in our function runner service caused error rates to increase across all Convex deployments between 8:20pm PT and 8:35pm PT. This change has been rolled back, and all deployments should be operating normally.
Text and vector search queries are failing for some deployments
The issue has been mitigated and we are rolling out a permanent fix.
This incident has been resolved.
We're currently investigating and monitoring increased error rates to/from database.
This incident has been resolved.
A small subset Convex instances are experiencing elevated errors rates. The Convex team is investigating.
The issue has been identified and the team is implementing a fix. Some affected deployments are back online
This incident has been resolved.
Some calls to AWS to deploy new versions of customer code are failing. Provisioning new preview deployments is also impacted. Live production traffic is unaffected.
We are continuing to investigate this issue.
We have deployed a fix and error rates are falling.
This incident has been resolved.
Some customers were unable to create Convex projects between 10:07am and 10:47am pacific, this has since been resolved.
Customers on one of our database clusters are experiencing elevated latency and error rates. We're investigating the cause.
Service was restored within 10 minutes to the affected deployments. The Convex team is monitoring the situation
This incident has been resolved.