- Level
- confirmed
- Worst impact
- Degraded
- Components
- US West 1
- Regions
- us
- Down Index
- 21of 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 1h it lasted.
Anything that failed between 2025-04-18 21:33 UTC and 2025-04-18 22:33 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
**04/18/2025 15:33 PDT Mitigated**: The delay in propagation for all configuration types in the US West region has been mitigated. Normal operation has resumed. **04/18/2025 14:33 PDT Investigating**: We observed delayed propagation of all configuration types in the US West region, with delays exceeding one minute. Server SDKs utilizing the Statsig CDN are not impacted. Traffic has been rerouted to ensure continuity as we investigated.
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-50e9c32c64
Is Statsig still down?
No, this incident was resolved 2025-04-18 22:33 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1h, from 2025-04-18 21:33 UTC to 2025-04-18 22:33 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.