Feature Flag Evaluation Errors (Statsig)

What to do

• Check whether you use Statsig US West 1, US East 1, US East 5, Europe West 1 and 1 more in apac, eu, us. 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 1h 9m it lasted.

  Anything that failed between 2026-07-09 01:28 UTC and 2026-07-09 02:36 UTC may need a replay.

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

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

Updates from Statsig 6

1. identifiedJul 9, 2026, 1:28 AM UTC

   Since approximately 1:56 PM PT on July 8 (20:56 UTC on July 8), customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. Specifically, launched Gates may have returned false instead of their expected default value. Our team identified the root cause as a recent code change and started a rollback of the affected services. We were actively working to confirm that evaluations returned by the V2 Config Delivery API were again showing expected defaults for launched Gates. V1 consumers were not affected. At the time of this update, no immediate customer action was required. We would provide the next update as more information became available.

   provider

2. identifiedJul 9, 2026, 1:29 AM UTC

   We are continuing to work on a fix for this issue.

   provider

3. identifiedJul 9, 2026, 1:35 AM UTC

   We are continuing to work on a fix for this issue.

   provider

4. identifiedJul 9, 2026, 1:39 AM UTC

   We are continuing to work on a fix for this issue.

   provider

5. monitoringJul 9, 2026, 2:15 AM UTC

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

   provider

6. resolvedJul 9, 2026, 2:36 AM UTC

   Between approximately 20:56 UTC on July 8 and 01:40 UTC on July 9, customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. During this window, launched Gates could return false instead of their expected default. V1 consumers were not affected. We identified the root cause as a recent change to config-spec generation. We rolled back the affected services across all regions and regenerated config payloads. We have verified that launched Gates are again returning their expected defaults, and all Config Delivery API components are now operational. No action is required to restore correct evaluation going forward. However, if your systems persisted data or took actions based on evaluations returned by the V2 Config Delivery API during the impact window, we recommend reviewing and reconciling that downstream data, as affected launched Gates may have returned false during that time.

   provider

Corrections

None so far.

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