Delayed Configuration Propagation

What to do

• Check whether you use Statsig US West 1, US East 1, US East 5, Europe West 1 and 1 more in apac, eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10h 13m it lasted.

  Anything that failed between 2026-03-11 10:38 UTC and 2026-03-11 20:51 UTC may need a replay.

• Subscribe to Statsig's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=statsig works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Statsig 2

1. investigatingMar 11, 2026, 10:38 AM 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.

   provider

2. resolvedMar 11, 2026, 8:51 PM UTC

   Resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.