Statsig experiencing propagation delays
Mar 30, 20:20 UTCMar 30, 22:10 UTC
Duration
1h 50m
Impact
Minor
Root cause
Not disclosed
Statsig, 90 days
3 incidents
Affected
US West 1US East 1US East 5Europe West 1Asia Southeast 1Config Delivery API - US West 1Config Delivery API - US East 1Config Delivery API - US East 5Config Delivery API - Europe West 1Config Delivery API - Asia Southeast 1
Final update
Resolved.
Timeline
- Resolved · Mar 30, 22:10 UTC
Resolved.
- Investigating · Mar 30, 20:20 UTC
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)
More from Statsig
Full historyAug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customerslasted 2d 17hDelayed Experiment & Feature Gate Results for Warehouse-Native (WHN) Customerslasted 0mWarehouse Native accounts may be experiencing export delays for data from Aug 6lasted 9h 14mFeature Flag Evaluation Errors (Statsig)lasted 1h 9mData ingestion delayedlasted 7h 38mWarehouse Native Pulse results delayed for customers with IP allowlists configuredlasted 0m