Statsig: Statsig experiencing propagation delays
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
From approximately 1:20PM PST to 3:10PM PST, we identified a code path that was creating write pressure on our redis cache which caused propagation to slow down. Resolution was resolved by mitigating the write pressure, and the team is following up on preventative measures to address the root cause. Systems are fully recovered at this point.
Mitigated: 03/30/2026 14:19:00 GMT-0700 (Pacific Daylight Time)
- 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
17d04045d5a0055d…
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-30 20:20 UTC, resolved after 1.8 h, 2 update(s).
- Title
- Statsig experiencing propagation delays
- Vendor
- Statsig
- Date
- URL
- https://rewindex.com/company/statsig/incidents/68jkf979fq1f
Statsig profileRecent Statsig incidentsAll outages on March 30, 2026Statsig in March 2026MarkdownJSON