Statsig: Data propagation delays

What to do

Check whether you use Statsig US West 1, US East 1, US East 5, Europe West 1 and 3 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 1m it lasted.
Anything that failed between 2025-10-31 21:52 UTC and 2025-10-31 21:53 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.

investigatingOct 31, 2025, 9:52 PM UTC
There were propagation delays across multiple regions caused by a bad config pushed earlier today, impacting the SDK and CDN. Additionally, there were also slower than real time ingestion speeds which affects data realtimeness in console surfaces such as diagnostics and dashboards. The team has identified the rootcause and system health has been restored.
provider
resolvedOct 31, 2025, 9:53 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 2025-10-31 21:53 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

1m, from 2025-10-31 21:52 UTC to 2025-10-31 21:53 UTC, by the times Statsig posted.

What was affected?

Statsig named US West 1, US East 1, US East 5, Europe West 1 and 3 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.