Skip to main content
Statsig

Elevated Latency for Cloudflare CDN

Degraded Lasted 4d 5h · started · Statsig's page

Level
confirmed
Worst impact
Degraded
Components
US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1
Regions
apac, eu, us
Down Index
35of 100

What to do

  • Check whether you use Statsig US West 1, US East 1, US East 5, Europe West 1 and 1 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 4d 5h it lasted.

    Anything that failed between 2026-01-27 01:44 UTC and 2026-01-31 07:25 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

    We are currently seeing elevated latency for server SDK configuration payloads at our Cloudflare CDN due to congestion at their edge hosts. We are working with them to mitigate the issue. Update: 01/30/2026 11:49AM PST We have seen some customers seeing latency improve with mitigated congestion. We're still working with Cloudflare to full resolve the issue for everyone. Update: 01/30/2026 11:25PM PST Latency has been restored to healthy, baseline levels.

    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-c2858642dd

Is Statsig still down?

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

How long did it last?

4d 5h, from 2026-01-27 01:44 UTC to 2026-01-31 07:25 UTC, by the times Statsig posted.

What was affected?

Statsig named US West 1, US East 1, US East 5, Europe West 1 and 1 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.