Convex incident

Some HTTP Actions returning 404

Minor Resolved View vendor source →

Convex experienced a minor incident on August 12, 2026 affecting Free & Starter and Professional and 1 more component, lasting 20m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 03:41 AM UTC
Resolved
Aug 12, 2026, 04:01 AM UTC
Duration
20m
Detected by Pingoru
Aug 12, 2026, 03:41 AM UTC

Affected components

Free & StarterProfessionalBusiness

Update timeline

  1. identified Aug 12, 2026, 03:41 AM 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. resolved Aug 12, 2026, 04:01 AM 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.