Delayed Configuration Propagation
Mar 11, 10:38 UTCMar 11, 20:51 UTC
Duration
10h 13m
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 11, 20:51 UTC
Resolved.
- Investigating · Mar 11, 10:38 UTC
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.
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