Statsig: Statsig experiencing propagation delays

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 1h 50m it lasted.
Anything that failed between 2026-03-30 20:20 UTC and 2026-03-30 22:10 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.

investigatingMar 30, 2026, 8:20 PM 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)
provider
resolvedMar 30, 2026, 10:10 PM UTC
Resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Statsig still down?

No, this incident was resolved 2026-03-30 22:10 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

1h 50m, from 2026-03-30 20:20 UTC to 2026-03-30 22:10 UTC, by the times Statsig posted.

What was affected?

Statsig named US West 1, US East 1, US East 5, Europe West 1 and 1 more in apac, eu, us.

What caused it?

Statsig hasn't published a root cause. If it does, it shows here.

Where does this come from?

Statsig's official status page, https://status.statsig.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.