Statsig: Investigating Config Propagation
Affected components: Event Forwarding Pipeline (Warehouse Native)Config Delivery API - US East 1US East 1Config Delivery API - US West 1US West 1Config Delivery API - US East 5US East 5
Timeline of updates
- investigating
We are currently investigating an issue affecting config propagation in the us-east5, us-east1, us-west1 regions. Some customers may be experiencing service interruptions or degraded performance. Diagnostic events are also delayed in these regions.
Our Infrastructure team is actively working to identify the root cause and restore normal operation. - 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
54adfc5fff0ea387…
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-01-26 17:34 UTC, resolved after 1 min, 2 update(s).
- Title
- Investigating Config Propagation
- Vendor
- Statsig
- Date
- URL
- https://rewindex.com/company/statsig/incidents/nkbxsxbtc3c3
Statsig profileRecent Statsig incidentsAll outages on January 26, 2026Statsig in January 2026MarkdownJSON