Convex Outage History

Convex is up right now

Convex had 44 outages in the last 2 years totaling 29h 6m of downtime — averaging 1.8 incidents per month.

There were 44 Convex outages since June 6, 2025 totaling 29h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.convex.dev

Minor June 10, 2026

Elevated error rate on some Pro deployments

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
  1. identified Jun 10, 2026, 12:18 AM UTC

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

  2. monitoring Jun 10, 2026, 12:20 AM UTC

    A fix has been implemented and we are monitoring the situation

  3. monitoring Jun 10, 2026, 12:53 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jun 10, 2026, 03:09 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 10, 2026, 03:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2026

Brief interruption in availability of some Convex deployments

Detected by Pingoru
May 30, 2026, 01:12 AM UTC
Resolved
May 30, 2026, 12:52 AM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Minor May 29, 2026

Subset of EU deployments seeing elevated errors

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
  1. investigating May 29, 2026, 03:23 PM UTC

    We are currently investigating.

  2. monitoring May 29, 2026, 04:47 PM UTC

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

  3. resolved May 29, 2026, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026

Custom domain creation encountering errors

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
  1. 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.

  2. resolved May 26, 2026, 06:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 22, 2026

HTTP Action Outage Affecting Some Deployments

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
  1. 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.

  2. 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.

  3. 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.

  4. 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 →

Major May 8, 2026

Intermittent Impact from AWS Outage

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
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 →

Minor May 6, 2026

Elevated latency for function calls for some deployments

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
  1. 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

  2. monitoring May 06, 2026, 06:04 PM UTC

    A fix has been implemented and we are monitoring the results

  3. resolved May 06, 2026, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 21, 2026

Login/Deployment/Dashboard services impacted

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
  1. investigating Apr 21, 2026, 04:23 PM UTC

    Database issue affecting our authentication, dashboard, and project deployment services. Your application live traffic is unaffected.

  2. monitoring Apr 21, 2026, 04:41 PM UTC

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

  3. monitoring Apr 21, 2026, 04:41 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 21, 2026, 04:56 PM UTC

    Login/Deployment/Dashboard services are confirmed restored

Read the full incident report →

Major April 9, 2026

Small percentage of deployments experiencing outage

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
  1. investigating Apr 09, 2026, 05:59 AM UTC

    Seems related to a problematic database failover. Updates soon.

  2. monitoring Apr 09, 2026, 06:05 AM UTC

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

  3. 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 →

Minor March 25, 2026

Some deployments are unavailable

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
  1. investigating Mar 25, 2026, 09:50 PM UTC

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

  2. monitoring Mar 25, 2026, 09:58 PM UTC

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

  3. resolved Mar 25, 2026, 10:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 25, 2026

elevated latency for a small subset of convex deployments

Detected by Pingoru
Mar 25, 2026, 04:27 PM UTC
Resolved
Mar 25, 2026, 07:46 PM UTC
Duration
3h 19m
Timeline · 4 updates
  1. investigating Mar 25, 2026, 04:27 PM UTC

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

  2. identified Mar 25, 2026, 05:54 PM UTC

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

  3. resolved Mar 25, 2026, 07:46 PM UTC

    This incident has been resolved.

  4. 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 →

Notice March 14, 2026

limited availability for provisioning new backends

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
  1. investigating Mar 14, 2026, 06:05 PM UTC

    Provisioning new backends is currently limited and will be resolved shortly

  2. monitoring Mar 14, 2026, 06:11 PM UTC

    Service is being restored

  3. resolved Mar 14, 2026, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 12, 2026

elevated error rates on convex for pro instances

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
  1. investigating Mar 12, 2026, 01:17 PM UTC

    We are currently investigating an issue leading to higher error rates

  2. monitoring Mar 12, 2026, 01:40 PM UTC

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

  3. resolved Mar 12, 2026, 01:55 PM UTC

    This incident has been resolved.

  4. 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 →

Notice February 25, 2026

downtime for a small subset of customers

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
  1. 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.

  2. resolved Feb 25, 2026, 01:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 10, 2026

Some custom domains not working

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
  1. 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.

  2. monitoring Feb 10, 2026, 01:31 AM UTC

    All hostnames have been reconfigured and should be available again.

  3. resolved Feb 10, 2026, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 7, 2026

Convex Dashboard Availability

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
  1. 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.

  2. monitoring Feb 07, 2026, 03:03 AM UTC

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

  3. resolved Feb 07, 2026, 03:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 5, 2026

authentication impacted for some users on non-pro plans

Detected by Pingoru
Feb 05, 2026, 12:28 AM UTC
Resolved
Feb 05, 2026, 12:37 AM UTC
Duration
8m
Timeline · 2 updates
  1. 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.

  2. resolved Feb 05, 2026, 12:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 28, 2026

some customers hitting OptimisticConcurrencyControlFailure on code pushes

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
  1. 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.

  2. 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

  3. resolved Jan 29, 2026, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 27, 2026

Increased error rate across all Convex deployments

Detected by Pingoru
Jan 27, 2026, 04:43 AM UTC
Resolved
Jan 27, 2026, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Minor January 17, 2026

Text and vector search unavailable for some deployments

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
  1. investigating Jan 17, 2026, 12:09 AM UTC

    Text and vector search queries are failing for some deployments

  2. monitoring Jan 17, 2026, 01:05 AM UTC

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

  3. resolved Jan 17, 2026, 02:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 9, 2026

Intermittent increased error rates

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
  1. investigating Jan 09, 2026, 12:51 AM UTC

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

  2. resolved Jan 09, 2026, 01:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 21, 2025

Elevated error rates for a subset of instances

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
  1. investigating Nov 21, 2025, 10:15 PM UTC

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

  2. 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

  3. resolved Nov 21, 2025, 10:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 14, 2025

Code Deployment Degraded

Detected by Pingoru
Nov 14, 2025, 09:29 PM UTC
Resolved
Nov 15, 2025, 12:42 AM UTC
Duration
3h 13m
Affected: Free & Starter
Timeline · 4 updates
  1. investigating Nov 14, 2025, 09:29 PM 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 Nov 14, 2025, 09:29 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 14, 2025, 11:05 PM UTC

    We have deployed a fix and error rates are falling.

  4. resolved Nov 15, 2025, 12:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 10, 2025

project creation was impacted

Detected by Pingoru
Nov 10, 2025, 06:52 PM UTC
Resolved
Nov 10, 2025, 06:07 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 10, 2025, 06:52 PM UTC

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

Read the full incident report →