Statsig Outage History

24 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Statsig status100.00% uptime history

Every Recorded Statsig Incident

Statsig incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 28, 2026Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) CustomersFull 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!65h 36mResolved
Aug 27, 2026Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) Customers-- 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…-2249 minResolved
Aug 7, 2026Warehouse Native accounts may be experiencing export delays for data from Aug 6This incident has been resolved9h 14mResolved
Jul 9, 2026Feature Flag Evaluation Errors (Statsig)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…1h 8mResolved
Jun 20, 2026Data ingestion delayedWarehouse native exposure forwarding has caught up.7h 37mResolved
Jun 16, 2026Warehouse Native Pulse results delayed for customers with IP allowlists configuredA 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…0 minResolved
May 26, 2026Statsig Console temporarily downResolved.24 minResolved
May 2, 2026Config Propagation Delay and Increased Error Rates for Console APIResolved.2h 14mResolved
Apr 17, 2026Elevated 401 unauthorized from statsigcdnResolved.12 minResolved
Apr 13, 2026Increased error rates affecting Console APIsResolved.6 minResolved
Mar 30, 2026Statsig experiencing propagation delaysResolved.1h 50mResolved
Mar 18, 2026Regional Issue for Statsig ConsoleResolved.40 minResolved
Mar 18, 2026Client SDK Success Rate in Southeast AsiaResolved.1h 3mResolved
Mar 11, 2026Delayed Configuration PropagationResolved.10h 13mResolved
Feb 25, 2026Statsig Console AvailabilityResolved.5 minResolved
Jan 27, 2026Elevated Latency for Cloudflare CDNResolved.101h 41mResolved
Jan 26, 2026Investigating Config PropagationResolved.1 minResolved
Jan 24, 2026Issues for Server SDKs in US-EAST and US-WESTResolved.1h 23mResolved
Jan 15, 2026Topline Alerts MisfiringResolved.1 minResolved
Jan 12, 2026Success Rate drop for US East RegionResolved.1h 54mResolved
Dec 11, 2025Slack Integration OversendingResolved.1h 38mResolved
Nov 18, 202511/18/2025 06:50:00 GMT-0800 (Pacific Standard Time)Resolved.1 minResolved
Nov 18, 202511/18/2025 05:00:00 GMT-0800 (Pacific Standard Time)Resolved.1h 42mResolved
Nov 7, 2025Client SDK Initialization and Event Logging Unavailable for 5 minutesResolved.5 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Statsig incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Statsig Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Statsig acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Statsig outage in this window ran 4d 5h, against a mean recovery of 9h 5m. If you depend on Statsig in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.