Search

Companies / Statsig / incidents

Statsig: Feature Flag Evaluation Errors (Statsig)

Impact: majorStatus: resolvedStarted Resolved (1.1 h)6 updatesSource: stspg.io (opens in new tab)
Summary

Statsig’s major V2 Config Delivery API incident was recorded starting 2026-07-09 01:28 UTC and resolved after 1 h 8 min. Launched Feature Gates could return false instead of defaults between 20:56 UTC on July 8 and 01:40 UTC on July 9; V1 was unaffected. A config-spec generation change caused the issue; affected services were rolled back.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Asia Southeast 1Config Delivery API - Asia Southeast 1Config Delivery API - US East 1US East 1Config Delivery API - US West 1US West 1Config Delivery API - US East 5US East 5Config Delivery API - Europe West 1Europe West 1

Timeline of updates

  1. identified

    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.

  2. identified

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

  3. identified

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

  4. identified

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

  5. monitoring

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

  6. resolved

    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.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Statsig profile · Recent Statsig incidents · Markdown · JSON