Companies/Convex/Incidents

Convex: Some HTTP Actions returning 404

Affected components: BusinessLive Traffic - BusinessLive Traffic - ProfessionalProfessionalFree & StarterLive Traffic - Free & Starter

Timeline of updates

1. identified2026-08-12 03:41 UTC

   We're investigating reports that HTTP Actions are returning 404 responses when an X-Forwarded-Host header is set on the incoming request. We've identified a potential infrastructure change and are reverting it now.

2. resolved2026-08-12 04:01 UTC

   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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Convex profileRecent Convex incidentsAll outages on August 12, 2026Convex in August 2026MarkdownJSON