Statsig outage, 11 November 2026
Delayed Config Propagation in Europe and Asia Regions
- Started
- Resolved
- 11 Nov 2026, 19:30 UTC - reported afterwards
- Impact
- Not stated
Is this still happening?
No. Statsig marked this incident resolved.
Right now: Statsig reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Statsig status
At a glance
- Statsig did not rate the impact of this incident.
- It was the first Statsig incident in 30 days.
- 3 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 2 May 2026.
Our summary from the Statsig incidents we have recorded since 31 Oct 2025 - how we count.
Last update from Statsig
Between 11:30 AM and 1:20 PM PST, Console changes were not delivered to SDKs served from our europe-west1 and asia-southeast1 regions, so SDKs in these regions continued serving the last known configuration. The issue has been resolved and SDKs have picked up the latest configuration. No action is required on your end. We apologize for any inconvenience this may have caused.
Similar Statsig incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h 14 min
Config Propagation Delay and Increased Error Rates for Console API
-
, resolved after 10 h 13 min
Delayed Configuration PropagationPostmortem
-
, resolved after 1 min
Other recent Statsig incidents
-
Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) CustomersPostmortem
-
Warehouse Native accounts may be experiencing export delays for data from Aug 6
-
Feature Flag Evaluation Errors (Statsig)Postmortem
-
Warehouse Native Pulse results delayed for customers with IP allowlists configured
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.