- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Log Event API
- Regions
- eu, us
What to do
Check whether you use Statsig Log Event API in 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 17m it lasted.
Anything that failed between 2025-06-06 18:53 UTC and 2025-06-06 19: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.
Updates from Statsig 2
- investigating
**06/06/2025 12:10 PDT Mitigated**: US East1 has been fully drained, and customers should see normal levels of 5xx again. **06/06/2025 12:01 PDT Investigating**: EU West has fully recovered, and traffic in US East is showing signs of improvement. **06/06/2025 11:53 PDT Investigating**: Elevated 5xx errors are occurring in the US East and EU West regions, with the recovery process underway.
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-dcdd3f329a
Is Statsig still down?
No, this incident was resolved 2025-06-06 19:10 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
17m, from 2025-06-06 18:53 UTC to 2025-06-06 19:10 UTC, by the times Statsig posted.
What was affected?
Statsig named Log Event API in 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.