- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Statsig. 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 38m it lasted.
Anything that failed between 2025-12-11 19:52 UTC and 2025-12-11 21:30 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
- investigating
Customers with multiple Slack channels configured are receiving messages in all channels, instead of only those filtered to the individual channel. We are investigating the issue. Mitigated: 12/11/2025 1:30:00 GMT-0800 (Pacific Standard Time)
provider
- resolved
Resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b4e9412676
Is Statsig still down?
No, this incident was resolved 2025-12-11 21:30 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1h 38m, from 2025-12-11 19:52 UTC to 2025-12-11 21:30 UTC, by the times Statsig posted.
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.