- Level
- confirmed
- Worst impact
- Degraded
- Components
- Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native)
- Down Index
- 21of 100
What to do
Check whether you use Statsig Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native). 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 10m it lasted.
Anything that failed between 2025-05-31 01:20 UTC and 2025-05-31 02: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
**05/30/2025 19:30 PDT Mitigated**: Streaming data is continued towards full recovery. **05/30/2025 18:55 PDT Recovering**: The cause of the data delay has been addressed. Streaming data is now in the process of recovery. **05/30/2025 18:20 PDT Investigating**: Data delays are impacting streaming pipelines, affecting real-time features such as Metrics Explorer.
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-bf51159e94
Is Statsig still down?
No, this incident was resolved 2025-05-31 02:30 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1h 10m, from 2025-05-31 01:20 UTC to 2025-05-31 02:30 UTC, by the times Statsig posted.
What was affected?
Statsig named Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native).
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.