Statsig Status Status Page

Aug 26, 2026 · resolved Aug 26

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

Aug 7, 2026 · resolved Aug 8

This incident has been resolved

Jul 9, 2026 · resolved Jul 9

Between approximately 20:56 UTC on July 8 and 01:40 UTC on July 9, customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. During this window, launched Gates could return false instead of their expected default. V1 consumers were not affected. We identified the root cause as a recent change to config-spec generation. We rolled back the affected services across all regions and regenerated config payloads. We have verified that launched Gates are again returning their expected defaults, and all Config Delivery API components are now operational. No action is required to restore correct evaluation going forward. However, if your systems persisted data or took actions based on evaluations returned by the V2 Config Delivery API during the impact window, we recommend reviewing and reconciling that downstream data, as affected launched Gates may have returned false during that time.

Jun 20, 2026 · resolved Jun 20

Warehouse native exposure forwarding has caught up.

Jun 11, 2026 · resolved Jun 16

A recent infra change spun up WHN compute with public IPs instead of routing through our published NAT ranges. Pulse traffic briefly left from an IP address which isn't in our published list. We've fixed routing; egress is back on the published IPs. No allowlist change needed.

Is Statsig Status down right now?

No — Statsig Status is up. All systems operational as of Aug 28, 1:47 AM UTC.

What is Statsig Status's current status?

Statsig Status: All Systems Operational. Alert24 checks Statsig Status's status page continuously and can notify you the moment it changes.

How do I get alerted when Statsig Status goes down?

Alert24 monitors Statsig Status and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.