- Level
- confirmed
- Worst impact
- Degraded
- Components
- US West 1
- Regions
- us
- Down Index
- 14of 100
What to do
Check whether you use Statsig US West 1 in 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 1m it lasted.
Anything that failed between 2025-07-28 19:15 UTC and 2025-07-28 19:16 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
The team has placed a number of mitigations in place for prevention based on the symptoms we understand from the incident. We are continuing to gather information for the full understanding of the incident. Mitigated: 07/14/2025 09:40: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-f8a9c590a5
Is Statsig still down?
No, this incident was resolved 2025-07-28 19:16 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1m, from 2025-07-28 19:15 UTC to 2025-07-28 19:16 UTC, by the times Statsig posted.
What was affected?
Statsig named US West 1 in 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.