outages.live
Live

Convex

Convex is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

7

Days with an incident

9

Median duration

54 min

Longest incident

1 h 53 min

Components

8

Development Services

Free & Starter Operational
90 days ago3 days with an incidentToday
Professional Operational
90 days ago3 days with an incidentToday
Business Operational
90 days ago3 days with an incidentToday

Live Traffic

Free & Starter Operational
90 days ago2 days with an incidentToday
Professional Operational
90 days ago2 days with an incidentToday
Business Operational
90 days ago3 days with an incidentToday
convex.dev website Operational
90 days agoNo incidentsToday
AI Gateway Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration54 min14:32 to 15:26Elevated Error Rate for Deploying Node ActionsDegraded

This issue is resolved, we are continuing to monitor.

Oct 9, 2026

Duration36 min22:33 to 23:09Failing function callsPartial outage

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.

Sep 28, 2026

Duration1 h 4 min21:09 to 22:13AI gateway unavailableMajor outage

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.

Sep 18, 2026

Duration1 h 7 min23:01 to 00:07Dashboard logins degradedNotice

This incident has been resolved.

Aug 16, 2026

Duration1 h 53 min23:33 to 01:26Account verification/team invite emails not workingPartial outage

This incident has been resolved.

Aug 12, 2026

Duration20 min03:41 to 04:01Some HTTP Actions returning 404Degraded

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 configuration made it read that header instead of the request's own hostname, so it looked for the wrong deployment. We reverted the change in all regions and error rates are back to their normal level. No data was lost, and requests that did not carry that header were unaffected. We are sorry for the disruption, and are improving our testing and monitoring of edge configuration changes to catch issues like this before they reach production.

Aug 5, 2026

Duration15 min01:42 to 01:57Action failures for business deployments that use createFunctionHandlePartial outage

This incident has been resolved.

Follow Convex

Your coding agent knows when Convex is down, and tells you when a failure is theirs, not yours. You can also get Convex incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "convex" and tell me if Convex has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=convex
Slack
/feed subscribe https://outages.live/feed.xml?providers=convex

Go from tracking outages to fixing production issues with Polylane.

Try Polylane