Skip to main content
Statsig

US East5 Latency Increase for Server SDK Initialization

Degraded Lasted 3h 40m · started · Statsig's page

Level
confirmed
Worst impact
Degraded
Components
US East 5
Regions
us

What to do

  • Check whether you use Statsig US East 5 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 3h 40m it lasted.

    Anything that failed between 2025-08-06 11:46 UTC and 2025-08-06 15:26 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

  1. investigating

    The team has identified a latency regression in our US East5 API Gateway that started at approximately 4:46am to 8:26am. The issue is now resolved.

    provider

  2. 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-f892e4b52b

Is Statsig still down?

No, this incident was resolved 2025-08-06 15:26 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

3h 40m, from 2025-08-06 11:46 UTC to 2025-08-06 15:26 UTC, by the times Statsig posted.

What was affected?

Statsig named US East 5 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.