Skip to main content
Statsig

Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers

Degraded Lasted 2d 17h · started · Statsig's page

Level
confirmed
Worst impact
Degraded
Components
Event Forwarding Pipeline (Warehouse Native)
Down Index
25of 100

What to do

  • Check whether you use Statsig 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 2d 17h it lasted.

    Anything that failed between 2026-08-28 22:40 UTC and 2026-08-31 16:17 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. monitoring

    Follow up to the Aug 26 issue impacting Warehouse-Native (WHN) customers: https://status.statsig.com/incidents/prtl9797v2y0 We recently identified a sub-issue affecting the export of exposure data for certain Feature Gates, specifically those gates without an associated metric, with 100%/0% rollout etc where no analytics is turned on. For these Feature Gates, the exposures for August 25 onward may still be missing or incomplete in your warehouse. Experiment exposures, live event ingestion, and the Exposure Stream are unaffected. Underlying exposure data has not been lost and is being backfilled. We have identified the root cause, deployed a fix, and are actively backfilling affected data for impacted customers. No action is needed and no reload is needed. Customers can expect/monitor those gates' exposure landed into their warehouse in the next two days.

    provider

  2. resolved

    Full 8/25–8/27 recovery is complete. For the gates with no metrics attached, exposures for 8/25–8/27 should now be available in the warehouse!

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

Is Statsig still down?

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

How long did it last?

2d 17h, from 2026-08-28 22:40 UTC to 2026-08-31 16:17 UTC, by the times Statsig posted.

What was affected?

Statsig named 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.