- Detected by Pingoru
- Jun 15, 2026, 10:23 PM UTC
- Resolved
- Jun 15, 2026, 10:35 PM UTC
- Duration
- 12m
Affected: Free & StarterProfessionalBusiness
Timeline · 5 updates
-
investigating Jun 15, 2026, 10:23 PM UTC
We are currently investigating this issue.
-
identified Jun 15, 2026, 10:26 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 15, 2026, 10:28 PM UTC
A fix has been implemented and error rates have gone down.
-
monitoring Jun 15, 2026, 10:31 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 15, 2026, 10:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2026, 04:49 AM UTC
- Resolved
- Jun 13, 2026, 04:53 AM UTC
- Duration
- 4m
Affected: Free & StarterFree & Starter
Timeline · 2 updates
-
monitoring Jun 13, 2026, 04:49 AM UTC
A failure in our load balancing layer caused a brief spike in error rates for Convex Free and Starter deployments. The affected service has recovered and we're monitoring to ensure error rates are back to zero.
-
resolved Jun 13, 2026, 04:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 12:00 AM UTC
- Resolved
- Jun 10, 2026, 03:09 AM UTC
- Duration
- 3h 9m
Affected: ProfessionalProfessional
Timeline · 5 updates
-
identified Jun 10, 2026, 12:18 AM UTC
We're investigating elevated error rates on a subset of Professional deployments
-
monitoring Jun 10, 2026, 12:20 AM UTC
A fix has been implemented and we are monitoring the situation
-
monitoring Jun 10, 2026, 12:53 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Jun 10, 2026, 03:09 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 10, 2026, 03:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 30, 2026, 01:12 AM UTC
- Resolved
- May 30, 2026, 12:52 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 30, 2026, 01:12 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 03:23 PM UTC
- Resolved
- May 29, 2026, 05:09 PM UTC
- Duration
- 1h 45m
Affected: ProfessionalProfessional
Timeline · 3 updates
-
investigating May 29, 2026, 03:23 PM UTC
We are currently investigating.
-
monitoring May 29, 2026, 04:47 PM UTC
A fix has been implemented. Monitoring to ensure error rates are down on all affected deployments
-
resolved May 29, 2026, 05:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 05:48 PM UTC
- Resolved
- May 26, 2026, 06:55 PM UTC
- Duration
- 1h 7m
Affected: ProfessionalBusiness
Timeline · 2 updates
-
identified May 26, 2026, 05:48 PM UTC
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.
-
resolved May 26, 2026, 06:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 06:11 AM UTC
- Resolved
- May 22, 2026, 10:09 AM UTC
- Duration
- 3h 57m
Affected: Free & StarterProfessional
Timeline · 4 updates
-
identified May 22, 2026, 06:11 AM UTC
The team has identified the issue and is reverting the change. We'll update on status as we resolve for the affected Convex customers.
-
identified May 22, 2026, 06:55 AM UTC
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.
-
monitoring May 22, 2026, 07:47 AM UTC
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.
-
resolved May 22, 2026, 10:09 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 12:16 AM UTC
- Resolved
- May 08, 2026, 02:05 AM UTC
- Duration
- 1h 49m
Affected: Free & StarterFree & StarterProfessionalBusinessProfessionalBusiness
Timeline · 5 updates
-
investigating May 08, 2026, 12:16 AM UTC
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.
-
identified May 08, 2026, 12:29 AM UTC
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.
-
identified May 08, 2026, 12:54 AM UTC
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.
-
monitoring May 08, 2026, 01:51 AM UTC
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.
-
resolved May 08, 2026, 02:05 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 05:43 PM UTC
- Resolved
- May 06, 2026, 06:24 PM UTC
- Duration
- 41m
Affected: Free & StarterProfessional
Timeline · 3 updates
-
investigating May 06, 2026, 05:43 PM UTC
Convex on-call engineers are investigated elevated latency for function calls on a small set of Convex deployments
-
monitoring May 06, 2026, 06:04 PM UTC
A fix has been implemented and we are monitoring the results
-
resolved May 06, 2026, 06:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 04:04 PM UTC
- Resolved
- Apr 21, 2026, 04:56 PM UTC
- Duration
- 52m
Affected: Free & StarterProfessionalBusiness
Timeline · 4 updates
-
investigating Apr 21, 2026, 04:23 PM UTC
Database issue affecting our authentication, dashboard, and project deployment services. Your application live traffic is unaffected.
-
monitoring Apr 21, 2026, 04:41 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 21, 2026, 04:41 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 21, 2026, 04:56 PM UTC
Login/Deployment/Dashboard services are confirmed restored
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 05:42 AM UTC
- Resolved
- Apr 09, 2026, 06:24 AM UTC
- Duration
- 42m
Affected: Free & StarterFree & StarterProfessionalBusinessProfessionalBusiness
Timeline · 3 updates
-
investigating Apr 09, 2026, 05:59 AM UTC
Seems related to a problematic database failover. Updates soon.
-
monitoring Apr 09, 2026, 06:05 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 09, 2026, 06:24 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 09:50 PM UTC
- Resolved
- Mar 25, 2026, 10:17 PM UTC
- Duration
- 27m
Affected: Free & StarterFree & Starter
Timeline · 3 updates
-
investigating Mar 25, 2026, 09:50 PM UTC
An unplanned database promotion has caused some deployments to become unavailable. We're investigating now.
-
monitoring Mar 25, 2026, 09:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 25, 2026, 10:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 04:27 PM UTC
- Resolved
- Mar 25, 2026, 07:46 PM UTC
- Duration
- 3h 19m
Timeline · 4 updates
-
investigating Mar 25, 2026, 04:27 PM UTC
We're investigating elevated latency for functions on a subset of Convex deployments
-
identified Mar 25, 2026, 05:54 PM UTC
A small subset of free instances are experiencing availability issues while we restore service.
-
resolved Mar 25, 2026, 07:46 PM UTC
This incident has been resolved.
-
postmortem Mar 25, 2026, 07:47 PM UTC
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!
Read the full incident report →
- Detected by Pingoru
- Mar 14, 2026, 06:09 PM UTC
- Resolved
- Mar 14, 2026, 06:10 PM UTC
- Duration
- 21s
Affected: Free & Starter
Timeline · 3 updates
-
investigating Mar 14, 2026, 06:05 PM UTC
Provisioning new backends is currently limited and will be resolved shortly
-
monitoring Mar 14, 2026, 06:11 PM UTC
Service is being restored
-
resolved Mar 14, 2026, 06:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 01:17 PM UTC
- Resolved
- Mar 12, 2026, 01:55 PM UTC
- Duration
- 37m
Affected: Free & Starter
Timeline · 4 updates
-
investigating Mar 12, 2026, 01:17 PM UTC
We are currently investigating an issue leading to higher error rates
-
monitoring Mar 12, 2026, 01:40 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 01:55 PM UTC
This incident has been resolved.
-
postmortem Mar 13, 2026, 03:36 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 05:28 PM UTC
- Resolved
- Mar 04, 2026, 06:28 PM UTC
- Duration
- 1h
Affected: Free & Starter
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 01:43 AM UTC
- Resolved
- Feb 25, 2026, 01:47 AM UTC
- Duration
- 4m
Affected: Free & Starter
Timeline · 2 updates
-
identified Feb 25, 2026, 01:43 AM UTC
A small subset of customers are currently experiencing downtime while we reprovision some hosts. We are working on restoring service.
-
resolved Feb 25, 2026, 01:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 01:26 AM UTC
- Resolved
- Feb 10, 2026, 02:01 AM UTC
- Duration
- 35m
Affected: Free & Starter
Timeline · 3 updates
-
identified Feb 10, 2026, 01:26 AM UTC
A misconfiguration caused many custom domains to stop working with a TLS error. We are rolling out a fix.
-
monitoring Feb 10, 2026, 01:31 AM UTC
All hostnames have been reconfigured and should be available again.
-
resolved Feb 10, 2026, 02:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 07, 2026, 02:50 AM UTC
- Resolved
- Feb 07, 2026, 03:06 AM UTC
- Duration
- 15m
Affected: Free & Starter
Timeline · 3 updates
-
identified Feb 07, 2026, 02:50 AM UTC
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.
-
monitoring Feb 07, 2026, 03:03 AM UTC
Error rates are back to baseline. We’re monitoring for stability, but the incident appears resolved.
-
resolved Feb 07, 2026, 03:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 12:28 AM UTC
- Resolved
- Feb 05, 2026, 12:37 AM UTC
- Duration
- 8m
Timeline · 2 updates
-
identified Feb 05, 2026, 12:28 AM UTC
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.
-
resolved Feb 05, 2026, 12:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 10:40 PM UTC
- Resolved
- Jan 29, 2026, 01:09 AM UTC
- Duration
- 2h 28m
Affected: Free & Starter
Timeline · 3 updates
-
investigating Jan 28, 2026, 10:40 PM UTC
Some customers are currently unable to push new code without hitting an OptimisticConcurrencyControlFailure error. We're investigating and working on resolving.
-
identified Jan 28, 2026, 10:51 PM UTC
We've identified a fix and are rolling it out to a subset of customers before deploying more widely
-
resolved Jan 29, 2026, 01:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 04:43 AM UTC
- Resolved
- Jan 27, 2026, 04:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 27, 2026, 04:43 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 17, 2026, 12:09 AM UTC
- Resolved
- Jan 17, 2026, 02:03 AM UTC
- Duration
- 1h 54m
Affected: Free & Starter
Timeline · 3 updates
-
investigating Jan 17, 2026, 12:09 AM UTC
Text and vector search queries are failing for some deployments
-
monitoring Jan 17, 2026, 01:05 AM UTC
The issue has been mitigated and we are rolling out a permanent fix.
-
resolved Jan 17, 2026, 02:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 12:51 AM UTC
- Resolved
- Jan 09, 2026, 01:40 AM UTC
- Duration
- 48m
Affected: Free & Starter
Timeline · 2 updates
-
investigating Jan 09, 2026, 12:51 AM UTC
We're currently investigating and monitoring increased error rates to/from database.
-
resolved Jan 09, 2026, 01:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 10:15 PM UTC
- Resolved
- Nov 21, 2025, 10:22 PM UTC
- Duration
- 6m
Affected: Free & Starter
Timeline · 3 updates
-
investigating Nov 21, 2025, 10:15 PM UTC
A small subset Convex instances are experiencing elevated errors rates. The Convex team is investigating.
-
identified Nov 21, 2025, 10:19 PM UTC
The issue has been identified and the team is implementing a fix. Some affected deployments are back online
-
resolved Nov 21, 2025, 10:22 PM UTC
This incident has been resolved.
Read the full incident report →
