- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US East 1
- Regions
- us
- Down Index
- 28of 100
What to do
Check whether you use Statsig US East 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 11m it lasted.
Anything that failed between 2025-07-18 15:10 UTC and 2025-07-18 15:21 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
At approximately, 8:10AM PST, we detected a growing rate of 5xx in our US East region. We have shifted traffic, and expect things to recover fully in a few minutes. Mitigated: 07/18/2025 08:21:00 GMT-0700 (Pacific Daylight Time): The traffic shift has completed and things should be recovered. Update: 10:49AM PST, the rootcause was identified to be a GCP Outage: https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J
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-79d2308a3d
Is Statsig still down?
No, this incident was resolved 2025-07-18 15:21 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
11m, from 2025-07-18 15:10 UTC to 2025-07-18 15:21 UTC, by the times Statsig posted.
What was affected?
Statsig named US East 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.