Some HTTP Actions returning 404

What to do

• Check whether you use Convex Free & Starter, Professional, Business. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.

  Anything that failed between 2026-08-12 03:41 UTC and 2026-08-12 04:01 UTC may need a replay.

• Subscribe to Convex's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=convex works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Convex 2

1. identifiedAug 12, 2026, 3: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.

   provider

2. resolvedAug 12, 2026, 4: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.