Statsig outage, 9 July 2026

Feature Flag Evaluation Errors (Statsig)

Started
Resolved
9 Jul 2026, 02:36 UTC (after 1 h 8 min)
Impact
Major
Affected
US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Last update from Statsig

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...

9 Jul 2026, 02:36 UTC

Read the full incident on the official Statsig status page

Is Statsig down now?

This page is the record of one past incident. For the live status, see Is Statsig down right now? - it reads the official status page every 2 minutes.

Other Statsig incidents

  1. Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers

  2. Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) Customers

  3. Warehouse Native accounts may be experiencing export delays for data from Aug 6

  4. Data ingestion delayed

  5. Warehouse Native Pulse results delayed for customers with IP allowlists configured

  6. Statsig Console temporarily down

  7. Config Propagation Delay and Increased Error Rates for Console API

  8. Elevated 401 unauthorized from statsigcdn

All recorded Statsig incidents