Convex Outage History

51 incidents recorded over the last 365 days, 51 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Convex Incident

Convex incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 16, 2026Account verification/team invite emails not workingThis incident has been resolved.1h 53mResolved
Aug 12, 2026Some HTTP Actions returning 404This 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…20 minResolved
Aug 5, 2026Action failures for business deployments that use createFunctionHandleThis incident has been resolved.14 minResolved
Jul 15, 2026New deployments unable to push Node Actions to ConvexThis 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…57 minResolved
Jun 23, 2026Availability issues across all Convex deploymentsWe 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…4 minResolved
Jun 18, 2026Automatic backups are not runningThis incident has been resolved.1h 18mResolved
Jun 15, 2026High error rates across all deployments, except some D1024sThis incident has been resolved.12 minResolved
Jun 13, 2026Spike in error rates for Convex Free and Starter deploymentsThis incident has been resolved.4 minResolved
Jun 10, 2026Elevated error rate on some Pro deploymentsThis incident has been resolved.2h 51mResolved
May 30, 2026Brief interruption in availability of some Convex deploymentsA 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…-20 minResolved
May 29, 2026Subset of EU deployments seeing elevated errorsThis incident has been resolved.1h 45mResolved
May 26, 2026Custom domain creation encountering errorsThis incident has been resolved.1h 7mResolved
May 22, 2026HTTP Action Outage Affecting Some DeploymentsAll 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.3h 57mResolved
May 8, 2026Intermittent Impact from AWS OutageWe’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…1h 49mResolved
May 6, 2026Elevated latency for function calls for some deploymentsThis incident has been resolved.41 minResolved
Apr 21, 2026Login/Deployment/Dashboard services impactedLogin/Deployment/Dashboard services are confirmed restored33 minResolved
Apr 9, 2026Small percentage of deployments experiencing outageThis 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…42 minResolved
Mar 25, 2026Some deployments are unavailableThis incident has been resolved.27 minResolved
Mar 25, 2026elevated latency for a small subset of convex deploymentsWe 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…3h 19mResolved
Mar 14, 2026limited availability for provisioning new backendsThis incident has been resolved.0 minResolved
Mar 12, 2026elevated error rates on convex for pro instancesAt 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…37 minResolved
Mar 4, 2026high error rates on customer backendsConvex 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…1h 0mResolved
Feb 25, 2026downtime for a small subset of customersThis incident has been resolved.4 minResolved
Feb 10, 2026Some custom domains not workingThis incident has been resolved.35 minResolved
Feb 7, 2026Convex Dashboard AvailabilityThis incident has been resolved.15 minResolved
Feb 5, 2026authentication impacted for some users on non-pro plansThis incident has been resolved.8 minResolved
Jan 28, 2026some customers hitting OptimisticConcurrencyControlFailure on code pushesThis incident has been resolved.2h 28mResolved
Jan 27, 2026Increased error rate across all Convex deploymentsA 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…-13 minResolved
Jan 27, 2026Increased error rate across all Convex deploymentsA 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…-13 minResolved
Jan 17, 2026Text and vector search unavailable for some deploymentsThis incident has been resolved.1h 54mResolved
Jan 9, 2026Intermittent increased error ratesThis incident has been resolved.48 minResolved
Nov 21, 2025Elevated error rates for a subset of instancesThis incident has been resolved.6 minResolved
Nov 14, 2025Code Deployment DegradedThis incident has been resolved.3h 13mResolved
Nov 10, 2025project creation was impactedSome customers were unable to create Convex projects between 10:07am and 10:47am pacific, this has since been resolved.-45 minResolved
Nov 5, 2025elevated latency/errors for a subset of customersThis incident has been resolved.16 minResolved
Nov 3, 2025elevated latency/errors for a subset of customersThis incident has been resolved.1h 17mResolved
Oct 31, 2025elevated latency/errors for a subset of customersThis incident has been resolved.47 minResolved
Oct 30, 2025elevated latency/errors for a subset of customersThis incident has been resolved.8h 8mResolved
Oct 28, 2025elevated latency/errors for a subset of customersThis 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…2h 12mResolved
Oct 25, 2025Errors affecting some instancesThis incident has been resolved.4h 19mResolved
Oct 20, 2025Convex Platform Login is DegradedThis incident has been resolved.5h 4mResolved
Oct 20, 2025node actions intermittently unavailableThis incident has been resolved.8h 24mResolved
Oct 20, 2025Usage info on Convex dashboard is unavailableThis incident has been resolved.7h 11mResolved
Oct 20, 2025Many Convex backends are downThis incident has been resolved.2h 16mResolved
Oct 3, 2025project creation and dashboard unavailableProject 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…14 minResolved
Oct 2, 2025Some Convex deployments had downtimeA bug in our downstream infrastructure provider caused a database cluster to deadlock when it was being resized.-232 minResolved
Sep 20, 2025Convex traffic having downtimeFrom 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…57 minResolved
Sep 8, 2025intermittent availability issues provisioning projectsThis incident has been resolved.47 minResolved
Sep 4, 2025Database maintenanceThis incident has been resolved.6 minResolved
Aug 31, 2025Database maintenance affecting a portion of non-pro instancesThis incident has been resolved.3h 45mResolved
Aug 30, 2025database maintenance affecting a subset of non-pro instancesThis incident has been resolved.9 minResolved

How to Read This Convex Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Convex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Convex outage in this window ran 8h 24m, against a mean recovery of 1h 43m. If you depend on Convex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.