- Level
- confirmed
- Worst impact
- Degraded
- Components
- Experiment Results (Cloud)
- Down Index
- 25of 100
What to do
Check whether you use Statsig Experiment Results (Cloud). Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16h 40m it lasted.
Anything that failed between 2025-10-02 17:20 UTC and 2025-10-03 10:00 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
We are aware of an issue where some feature gates may have a delay in Pulse results being available. The team is currently investigating and working on mitigating the issue. Further updates will be shared here. Mitigated: 10/03/2025 03:00:00 GMT-0700 (Pacific Daylight 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-a3f9f54615
Is Statsig still down?
No, this incident was resolved 2025-10-03 10:00 UTC. For Statsig's live state, see https://down.guide/providers/statsig.
How long did it last?
16h 40m, from 2025-10-02 17:20 UTC to 2025-10-03 10:00 UTC, by the times Statsig posted.
What was affected?
Statsig named Experiment Results (Cloud).
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.