Statsig: Data propagation delays
Affected components: Asia Southeast 1Config Delivery API - Asia Southeast 1Experiment Results (Cloud)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 5Config Delivery API - Europe West 1Europe West 1
Timeline of updates
- investigating
There were propagation delays across multiple regions caused by a bad config pushed earlier today, impacting the SDK and CDN. Additionally, there were also slower than real time ingestion speeds which affects data realtimeness in console surfaces such as diagnostics and dashboards. The team has identified the rootcause and system health has been restored.
- 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
5a2ba95f351b72f6…
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 2025-10-31 21:52 UTC, resolved after 1 min, 2 update(s).
- Title
- Data propagation delays
- Vendor
- Statsig
- Date
- URL
- https://rewindex.com/company/statsig/incidents/nvdl9c2p45b1
Statsig profileRecent Statsig incidentsAll outages on October 31, 2025Statsig in October 2025MarkdownJSON