- Level
- confirmed
- Worst impact
- Degraded
- Components
- US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1
- Regions
- apac, eu, us
- Down Index
- 30of 100
What to do
Check whether you use Statsig US West 1, US East 1, US East 5, Europe West 1 and 1 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 1h 34m it lasted.
Anything that failed between 2025-09-15 17:03 UTC and 2025-09-15 18:37 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
There was a regression affecting propagation times for some companies in all configuration types, leading to outdated evaluations through server SDKs. This has now been mitigated Mitigated: 09/15/2025 11:37: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-0211aaf663
Is Statsig still down?
No, this incident was resolved 2025-09-15 18:37 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1h 34m, from 2025-09-15 17:03 UTC to 2025-09-15 18:37 UTC, by the times Statsig posted.
What was affected?
Statsig named US West 1, US East 1, US East 5, Europe West 1 and 1 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.