Statsig: Investigating Config Propagation

What to do

Check whether you use Statsig US West 1, US East 1, US East 5, Event Forwarding Pipeline (Warehouse Native) in us, us-east1, us-east5, us-west1. 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 2026-01-26 17:34 UTC and 2026-01-26 17:35 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.

investigatingJan 26, 2026, 5:34 PM UTC
We are currently investigating an issue affecting config propagation in the us-east5, us-east1, us-west1 regions. Some customers may be experiencing service interruptions or degraded performance. Diagnostic events are also delayed in these regions. Our Infrastructure team is actively working to identify the root cause and restore normal operation.
provider
resolvedJan 26, 2026, 5:35 PM UTC
Resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Statsig still down?

No, this incident was resolved 2026-01-26 17:35 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

1m, from 2026-01-26 17:34 UTC to 2026-01-26 17:35 UTC, by the times Statsig posted.

What was affected?

Statsig named US West 1, US East 1, US East 5, Event Forwarding Pipeline (Warehouse Native) in us, us-east1, us-east5, us-west1.

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.