Live

Elevated errors for some deployments in US East region

0

Some Convex deployments in the US East (us-east-1) region had elevated errors and timeouts for queries, mutations and actions. The affected components are Free & Starter, Professional and Business, including Live Traffic. Convex reports that the incident is resolved and that it lasted 19 minutes.

State

Resolved

Started

Lasted

19 min

Worst impact

Partial outage

Timeline

4 updates
09:0109:0609:1009:1509:20
Partial outageUpdate postedTimes in UTC

Investigating

14 min 73%

Identified

3 min 16%

Monitoring

2 min 11%

Updates

Times in UTC

As posted by Convex

Resolved

This incident has been resolved.

Monitoring

We restored the affected deployments in US East, and error rates are back to normal as of 09:15 UTC. We are monitoring the database cluster to make sure that it stays stable.

Identified

We identified a problem with one of our database clusters and failed over to a healthy instance. Most affected deployments are back in service as of 09:06 UTC. We are restoring the remaining deployments in stages, and expect full recovery shortly.

Investigating

Starting at 08:42 UTC (00:42 PT), some Convex deployments in the US East (us-east-1) region have elevated error rates and timeouts for queries, mutations and actions. We've identified the problematic database and are working to restore service. Deployments in other regions are not affected.

Affected components

6
Free & StarterProfessionalBusinessLive Traffic - Free & StarterLive Traffic - ProfessionalLive Traffic - Business

Convex in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

54 min

This incident

64% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

1 h 7 min
median 54 min
90 days agoToday

Other Convex incidents

All incidents

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane