Statsig: Client SDK Initialization and Event Logging Unavailable for 5 minutes

What to do

Check whether you use Statsig US West 1, US East 1, US East 5, Log Event API and 2 more in apac, eu, 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 5m it lasted.
Anything that failed between 2025-11-07 00:33 UTC and 2025-11-07 00:38 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.

investigatingNov 7, 2025, 12:33 AM UTC
The engineering team is currently investigating. We are seeing high unavailability from 4:33PM PST, but mostly recovered by 4:38PM PST. Client SDK Initialization failed to initialize during this time period for a majority of requests, and event logging calls failed as well. However, we expect that most events will be recoverable due to SDK level retries. Mitigated: 11/06/2025 16:40:00 GMT-0800 (Pacific Standard Time)
provider
resolvedNov 7, 2025, 12:38 AM 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 2025-11-07 00:38 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

5m, from 2025-11-07 00:33 UTC to 2025-11-07 00:38 UTC, by the times Statsig posted.

What was affected?

Statsig named US West 1, US East 1, US East 5, Log Event API and 2 more in apac, eu, 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.