Convex

Affected: Free & Starter, Professional, Business

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 14:32 UTC

   We're experiencing an elevated error rate for some customers with deployments that use node actions.

2. investigating 2026-10-20 14:33 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-20 14:34 UTC

   We are continuing to investigate this issue.

4. investigating 2026-10-20 14:34 UTC

   We are continuing to investigate this issue.

5. identified 2026-10-20 14:49 UTC

   We've identified the issue and working to resolve it.

6. identified 2026-10-20 15:00 UTC

   We've identified a fix. We're actively deploying a fix and errors are decreasing.

7. resolved 2026-10-20 15:26 UTC

   This issue is resolved, we are continuing to monitor.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 22:33 UTC

   We are currently investigating reports of failing function calls.

2. monitoring 2026-10-09 22:57 UTC

   The system has recovered and we are continuing to monitor the results.

3. resolved 2026-10-09 23:09 UTC

   On 2026-10-09, between 22:11 and 22:52 UTC, some query and mutation executions running in us-east-1 failed to run. This outage was caused by a network issue at an upstream provider. The problem is now resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: AI Gateway

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-28 21:09 UTC

   We are currently investigating an issue that makes the AI gateway refuse requests.

2. monitoring 2026-09-28 21:49 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-28 22:13 UTC

   An issue with an upstream provider caused requests to the AI Gateway to be rejected. The issue has been resolved and service has been restored. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-18 23:01 UTC

   We're experiencing elevated error rates for dashboard logins due to an issue with a 3rd party provider. We'll provide updates here as the situation unfolds. Live deployments are not affected.

2. monitoring 2026-09-18 23:09 UTC

   Error rates have reduced and appear to be stable, we are monitoring the situation

3. resolved 2026-09-19 00:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-16 23:33 UTC

   We identified an ongoing issue that prevents emails sent from the Convex dashboard (e.g. team invitations and new account verification emails) from being sent. We are currently working on a fix.

2. monitoring 2026-08-17 00:50 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-17 01:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-12 03:41 UTC

   We're investigating reports that HTTP Actions are returning 404 responses when an `X-Forwarded-Host` header is set on the incoming request. We've identified a potential infrastructure change and are reverting it now.

2. resolved 2026-08-12 04:01 UTC

   This incident is resolved. Between 00:20 and 04:15 UTC on 12 August, some HTTP Actions returned a 404 response. This affected requests that reached Convex through an intermediate proxy or CDN, because those requests carry an `X-Forwarded-Host` header. A change to our edge...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Business

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-05 01:42 UTC

   We identified an issue that can lead to actions failing to execute when their code calls `createFunctionHandle` (https://docs.convex.dev/api/modules/server#createfunctionhandle). This issue only affects business deployments (Free, Starter and Professional users are not...

2. resolved 2026-08-05 01:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-15 05:35 UTC

   We're investigating reports that users are unable to push code containing new Node Actions to Convex deployments.

2. identified 2026-07-15 05:41 UTC

   We've identified the issue causing failures when pushing code that includes Node Actions and are rolling out a fix. Deployments without Node Actions are unaffected. Another update to follow as recovery is confirmed.

3. resolved 2026-07-15 06:33 UTC

   This incident has been resolved. We deployed a fix for the recent backend change that was causing pushes containing Node Actions to fail, and we've confirmed that pushes have returned to normal across all deployments. Pushes without Node Actions were unaffected throughout. No...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-23 18:13 UTC

   We're currently investigating an availability issue affecting Convex deployments and will provide an update in the near future.

2. investigating 2026-06-23 18:15 UTC

   We believe the issue to be resolved, currently monitoring.

3. resolved 2026-06-23 18:18 UTC

   We had approximately 10 minutes of availability impact caused by a cascading failure after performing a configuration change to migrate a database cluster. We apologize for the impact and will be refining these processes to avoid this happening again.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-18 21:44 UTC

   We identified an issue that prevents automatic cloud backups from running. Our engineers are working on a fix. In the meantime, it is possible to manually start backups from the dashboard “Backup & Restore” page.

2. monitoring 2026-06-18 22:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-18 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-15 22:23 UTC

   We are currently investigating this issue.

2. identified 2026-06-15 22:26 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-15 22:28 UTC

   A fix has been implemented and error rates have gone down.

4. monitoring 2026-06-15 22:31 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-15 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Free & Starter

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-13 04:49 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.

2. resolved 2026-06-13 04:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Professional, Professional

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-10 00:00 UTC

   We're investigating elevated error rates on a subset of Professional deployments

2. monitoring 2026-06-10 00:20 UTC

   A fix has been implemented and we are monitoring the situation

3. monitoring 2026-06-10 00:53 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-06-10 03:09 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-10 03:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-05-30 00:52 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.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Professional, Professional

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-29 15:23 UTC

   We are currently investigating.

2. monitoring 2026-05-29 16:47 UTC

   A fix has been implemented. Monitoring to ensure error rates are down on all affected deployments

3. resolved 2026-05-29 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Professional, Business

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-26 17:48 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...

2. resolved 2026-05-26 18:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-22 06:11 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.

2. identified 2026-05-22 06:55 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...

3. monitoring 2026-05-22 07:47 UTC

   We've reverted 100% of deployments, and a code deployment will resolve HTTP action issues. Please redeploy your projects with `npx convex dev` and `npx convex deploy` and your HTTP actions should begin working immediately. We'll wait to resolve this incident until we've...

4. resolved 2026-05-22 10:09 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.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Free & Starter, Professional, Business, Professional, Business

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 00:16 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...

2. identified 2026-05-08 00:29 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...

3. identified 2026-05-08 00:54 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...

4. monitoring 2026-05-08 01:51 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.

5. resolved 2026-05-08 02:05 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.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 17:43 UTC

   Convex on-call engineers are investigated elevated latency for function calls on a small set of Convex deployments

2. monitoring 2026-05-06 18:04 UTC

   A fix has been implemented and we are monitoring the results

3. resolved 2026-05-06 18:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Professional, Business

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-21 16:04 UTC

   Load issues are affecting our authentication, dashboard, and project deployment services. Your application live traffic is unaffected.

2. monitoring 2026-04-21 16:41 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-04-21 16:41 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-04-21 16:56 UTC

   Login/Deployment/Dashboard services are confirmed restored

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Free & Starter, Professional, Business, Professional, Business

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-09 05:42 UTC

   Seems related to a problematic database failover. Updates soon.

2. monitoring 2026-04-09 05:59 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-09 06:24 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...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter, Free & Starter

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 21:50 UTC

   An unplanned database promotion has caused some deployments to become unavailable. We're investigating now.

2. monitoring 2026-03-25 21:58 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-25 22:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 16:27 UTC

   We're investigating elevated latency for functions on a subset of Convex deployments

2. identified 2026-03-25 17:54 UTC

   A small subset of free instances are experiencing availability issues while we restore service.

3. resolved 2026-03-25 19:46 UTC

   This incident has been resolved.

4. postmortem 2026-03-25 19:47 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...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-14 18:05 UTC

   Provisioning new backends is currently limited and will be resolved shortly

2. monitoring 2026-03-14 18:09 UTC

   Service is being restored

3. resolved 2026-03-14 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-12 13:17 UTC

   We are currently investigating an issue leading to higher error rates

2. monitoring 2026-03-12 13:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-12 13:55 UTC

   This incident has been resolved.

4. postmortem 2026-03-13 03:36 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...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-04 17:28 UTC

   We are currently investigating an issue leading to elevated error rates on customer backends

2. monitoring 2026-03-04 18:14 UTC

   We've identified the issue and remediated the problem. We're monitoring before we declare the all clear.

3. resolved 2026-03-04 18:28 UTC

   Incident resolved. We're very sorry for the impact on your projects. Our team will be publishing a detailed postmortem soon.

4. postmortem 2026-03-05 18:14 UTC

   Convex had downtime for some customers caused by an anomalous load spike that pushed an internal service into a load-shedding mode, which then triggered an unexpected panic in a caching library we were using. Specifically the load triggered two queue management algorithms: CoDel...

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-25 01:43 UTC

   A small subset of customers are currently experiencing downtime while we reprovision some hosts. We are working on restoring service.

2. resolved 2026-02-25 01:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-10 01:26 UTC

   A misconfiguration caused many custom domains to stop working with a TLS error. We are rolling out a fix.

2. monitoring 2026-02-10 01:31 UTC

   All hostnames have been reconfigured and should be available again.

3. resolved 2026-02-10 02:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-07 02:50 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.

2. monitoring 2026-02-07 03:03 UTC

   Error rates are back to baseline. We’re monitoring for stability, but the incident appears resolved.

3. resolved 2026-02-07 03:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-05 00:28 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.

2. resolved 2026-02-05 00:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-28 22:40 UTC

   Some customers are currently unable to push new code without hitting an OptimisticConcurrencyControlFailure error. We're investigating and working on resolving.

2. identified 2026-01-28 22:51 UTC

   We've identified a fix and are rolling it out to a subset of customers before deploying more widely

3. resolved 2026-01-29 01:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-01-27 04:30 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.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-01-27 04:30 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.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-17 00:09 UTC

   Text and vector search queries are failing for some deployments

2. monitoring 2026-01-17 01:05 UTC

   The issue has been mitigated and we are rolling out a permanent fix.

3. resolved 2026-01-17 02:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-09 00:51 UTC

   We're currently investigating and monitoring increased error rates to/from database.

2. resolved 2026-01-09 01:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-21 22:15 UTC

   A small subset Convex instances are experiencing elevated errors rates. The Convex team is investigating.

2. identified 2025-11-21 22:19 UTC

   The issue has been identified and the team is implementing a fix. Some affected deployments are back online

3. resolved 2025-11-21 22:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-11-14 21:29 UTC

   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.

2. investigating 2025-11-14 21:29 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-14 23:05 UTC

   We have deployed a fix and error rates are falling.

4. resolved 2025-11-15 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-10 18:07 UTC

   Some customers were unable to create Convex projects between 10:07am and 10:47am pacific, this has since been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-05 22:37 UTC

   Customers on one of our database clusters are experiencing elevated latency and error rates. We're investigating the cause.

2. monitoring 2025-11-05 22:47 UTC

   Service was restored within 10 minutes to the affected deployments. The Convex team is monitoring the situation

3. resolved 2025-11-05 22:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-03 11:24 UTC

   Customers on one of our database clusters are experiencing elevated latency and error rates. We're investigating the cause.

2. investigating 2025-11-03 12:14 UTC

   We temporarily halted all activity on the affected database cluster to restore it to a healthy state, and are bringing affected customers back online now. Pro customers should see their deployments back online immediately, and we're working on restoring service to remaining...

3. monitoring 2025-11-03 12:23 UTC

   All Convex deployments on the affected database cluster are back online now. We're continuing to investigate the root cause of this outage and monitor for stability.

4. resolved 2025-11-03 12:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-31 14:25 UTC

   An issue is identified affecting a subset of deployments.

2. identified 2025-10-31 14:51 UTC

   Brought back pro deployments. Continuing to work on free

3. resolved 2025-10-31 15:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-30 23:43 UTC

   We're investigating an issue with a database cluster leading to degraded performance and higher error rates for affected deployments.

2. identified 2025-10-30 23:44 UTC

   We've restored affected pro deployments. Working on bringing back affected free deployments.

3. identified 2025-10-31 00:25 UTC

   we've brought back a subset of free deployments. Continuing to remediate.

4. identified 2025-10-31 03:08 UTC

   We're continuing to work on a fix for the issue. Expect another update in ~90 minutes.

5. monitoring 2025-10-31 04:24 UTC

   All deployments should be restored. We are monitoring the database to ensure it remains stable.

6. monitoring 2025-10-31 05:59 UTC

   There will be sporadic availability issues for a small subset of non-pro customers. We apologize for this impact. There was an issue with a downstream provider which resulted in a database cluster running with an inefficient table format. We're in the process of rewriting this...

7. monitoring 2025-10-31 06:00 UTC

   We are continuing to monitor for any further issues.

8. resolved 2025-10-31 07:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-28 21:38 UTC

   We're investigating an issue with a database cluster leading to degraded performance and higher error rates for affected deployments.

2. identified 2025-10-28 21:50 UTC

   Service has been restored to Pro customers and we're working on restoring free deployments.

3. resolved 2025-10-28 23:50 UTC

   This incident has been resolved. The specific cause was due to a maintenance operation from a downstream provider which resulted in a database cluster switching to using an unoptimized table format. We'll be working to ensure the underlying cause is resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-25 13:15 UTC

   We are currently investigating this issue.

2. investigating 2025-10-25 14:10 UTC

   Identified an issue. Remediating. Pro customers have been remediated fully. Continuing to monitor

3. resolved 2025-10-25 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 19:54 UTC

   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.

2. investigating 2025-10-20 22:05 UTC

   We are continuing to investigate this issue.

3. resolved 2025-10-21 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 19:14 UTC

   We're seeing note action availability problems due to AWS Lambda issues.

2. monitoring 2025-10-21 03:23 UTC

   Issue should be resolved. Monitoring to ensure things are working.

3. resolved 2025-10-21 03:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 14:48 UTC

   Usage information can't be queried at the moment; we believe this is caused by a new round of AWS issues.

2. identified 2025-10-20 19:20 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-10-20 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Affected: Free & Starter

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:22 UTC

   Many databases are currently broken due to an AWS outage in us-east-1

2. monitoring 2025-10-20 09:29 UTC

   AWS has mitigated the issue and services are recovering.

3. resolved 2025-10-20 09:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-03 09:36 UTC

   Project creation and the dashboard are currently down

2. resolved 2025-10-03 09:51 UTC

   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.

Excerpts are shortened. Read the full incident on Convex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-02 17:23 UTC

   A bug in our downstream infrastructure provider caused a database cluster to deadlock when it was being resized.

Excerpts are shortened. Read the full incident on Convex's status page.