outages.live
Live
ConvexIncident · 2026-09-28 21:09 UTC

AI gateway unavailable

ResolvedOfficial update

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.

The latest update from Convex.

State

Resolved

Started

34 d ago

2026-09-28 21:09 UTC

Lasted

1 h 4 min

until 2026-09-28 22:13 UTC

Worst impact

Major outage

Timeline

3 updates
21:0921:2521:4121:5722:13
Major outageUpdate postedTimes in UTC

Investigating

40 min 63%

Monitoring

24 min 37%

Updates

Times in UTC

As posted by Convex

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

Monitoring2026-09-28 21:49 UTC

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

Investigating2026-09-28 21:09 UTC

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

Affected components

1
AI Gateway

Convex in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

7

Days with an incident

9

Median duration

54 min

This incident

1.2× the median

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

1 h 53 min
median 54 min
90 days agoToday

Other Convex incidents

All incidents

Convex·Elevated Error Rate for Deploying Node Actions

This issue is resolved, we are continuing to monitor.

Resolvedresolved 12 d ago

Convex·Failing function calls

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.

Resolvedresolved 22 d ago

Convex·Dashboard logins degraded

This incident has been resolved.

Resolvedresolved 43 d ago

Convex·Account verification/team invite emails not working

This incident has been resolved.

Resolvedresolved 76 d ago

Convex·Some HTTP Actions returning 404

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.

Resolvedresolved 81 d ago

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.cc/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.cc/feed.xml?providers=convex
Slack
/feed subscribe https://outages.cc/feed.xml?providers=convex

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane