Skip to main content
Statsig

Data ingestion delayed

Degraded Lasted 7h 38m · started · Statsig's page

Level
confirmed
Worst impact
Degraded
Components
Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native)
Down Index
27of 100

What to do

  • Check whether you use Statsig Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native). 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 7h 38m it lasted.

    Anything that failed between 2026-06-20 03:22 UTC and 2026-06-20 11:00 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 3

  1. monitoring

    We have identified an issue from a recent change impacting BigQuery connectivity since 4:30pm PST. No data has been lost. We have rolled back the change and data ingestion is catching up. Experiment results for some customers may be delayed.

    provider

  2. monitoring

    Data ingestion has caught up and is operating normally. We are continuing to monitor warehouse native exposure forwarding delay.

    provider

  3. resolved

    Warehouse native exposure forwarding has caught up.

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

Is Statsig still down?

No, this incident was resolved 2026-06-20 11:00 UTC. For Statsig's live state, see https://down.guide/statsig.

How long did it last?

7h 38m, from 2026-06-20 03:22 UTC to 2026-06-20 11:00 UTC, by the times Statsig posted.

What was affected?

Statsig named Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native).

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.