- Level
- confirmed
- Worst impact
- Degraded
- Components
- US East 1
- Regions
- us
- Down Index
- 19of 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 25m it lasted.
Anything that failed between 2025-06-05 22:05 UTC and 2025-06-05 22:30 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/05/2025 15:30 PDT Mitigated**: Traffic has been rerouted from the affected cluster in East US to nearby regions. Configuration update propagation latency has stabilized. **06/05/2025 15:25 PDT Investigating**: Starting at 15:05 PDT, users in the East US region experienced delays in receiving new configuration updates via Client and Server SDKs following modifications in the Statsig Console or through the Console API.
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-8c27fb5d4a
Is Statsig still down?
No, this incident was resolved 2025-06-05 22:30 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
25m, from 2025-06-05 22:05 UTC to 2025-06-05 22:30 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.