Statsig: Delayed Configuration Propagation
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
- investigating
We are currently seeing issues with config propagation for server SDKs. The team is currently investigating and will provide updates soon.
Update: 12:37PM PST
The team has identified what the root cause is and is working on getting a fix deployed now. We are currently aiming for recovery around 1PM.
Update: 1:14PM PST
Most companies should see configuration propagating again, we are continuing to work on full recovery. Delay should at most be a few minutes at this point.
Update: 1:51PM PST
We continue to see config propagation hold at a steady state, the team is working on fast follow ups for prevention to ensure we can confidently mark the incident as resolved.
- resolved
Resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4efe6e7c42046fa6…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Statsig, started 2026-03-11 10:38 UTC, resolved after 10 h, 2 update(s).
- Title
- Delayed Configuration Propagation
- Vendor
- Statsig
- Date
- URL
- https://rewindex.com/company/statsig/incidents/7gdbj6qf2bny
Statsig profileRecent Statsig incidentsAll outages on March 11, 2026Statsig in March 2026MarkdownJSON