Is Statsig Down?

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! --- [2026-08-28T15:40:27.273-07:00] (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.

-- Only WHN customers are impacted -- Around 2026-08-26 2:30 PT (16:30 UTC), we were experiencing a delay in processing experiment and feature gate exposure data for Warehouse-Native (WHN) customers. As a result, experiment and feature gate results may show fewer participants than expected for August 25–26, and cumulative metric totals from August 25 onward may appear understated. Live event ingestion and the Exposure Stream are unaffected. Data is delayed, not lost. As of 2026-08-27, 06:53 PT, our team has identified the root cause and actively worked to backfill affected data and restored normal processing. The underlying data has now been reprocessed and delivered. - If your experiments are on a scheduled reload, no action is needed — the next scheduled run recalculates the affected dates automatically and restores the missing participants. Results should be complete after that run. - A reload is required in two cases. If an experiment/gate has already been stopped or concluded, its results will not update on their own and need a full reload. If you reload manually rather than on a schedule, please run a reload before 28 August so the recalculation covers both affected dates; after that a full reload is needed instead of an incremental one.

This incident has been resolved --- [2026-08-07T21:00:38.962-07:00] (monitoring) Thank you for your patience. The main query-intensive jobs are through now, but it also took quite a bit longer than before. Catch up for subsequent jobs may therefore take up to 3am PT to complete. Our sincere apologies for the delay and we will continue to share updates as we monitor the job completion. --- [2026-08-07T20:55:40.653-07:00] (monitoring) We are still making progress on re-running the exports. We should start to see some exports completing but the expected completion time for the full system to rerun has extended to 9pm PT. We will continue to keep you updated and aim to have the next update at 9pm PT! To clarify: 1. This only impacts customers who use Statsig warehouse native. If you are on Statsig cloud, you can ignore this status page. 2. For WHN customers, once we finish rerunning the final jobs, Statsig will automatically take care of refreshing the data for all experiments that are configured to incrementally refresh metrics. --- [2026-08-07T16:10:54.261-07:00] (monitoring) This issue only impacts customers on Warehouse Native on the echidna pipeline. Around 11 am PT, we have identified that WHN accounts will have event and exposure export delays from August 6. No data is lost as the job rebuilds the full day from source so there will be no gaps once the post-revert run lands. Everything through August 5 is intact. Around 1pm PT, we have implemented a fix that should have mitigated this issue. We expect exports to complete around 7pm PT.