We started checking Statsig on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Statsig reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Statsig's own status page declared. Below it, any public chatter we saw about Statsig and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Statsig's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Statsig in the last 24 hours, which is not evidence that nothing is wrong.
Statsig's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Statsig's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Statsig next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
446
US-West
100.00%
342
Europe
100.00%
313
Asia-Pacific
100.00%
189
Their declared record
Statsig's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) CustomersMinor incident
Aug 28, 2026, 10:40 PM UTC to Aug 31, 2026, 4:17 PM UTC (2d 17h)resolved
their latest update (Aug 31, 2026, 4:17 PM UTC): 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!
Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) CustomersAll systems operational
Aug 26, 2026, 9:30 AM UTC to Aug 26, 2026, 9:30 AM UTC (0 min)resolved
their latest update (Aug 26, 2026, 9:30 AM UTC): -- 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 t…
Warehouse Native accounts may be experiencing export delays for data from Aug 6Minor incident
Aug 7, 2026, 11:10 PM UTC to Aug 8, 2026, 8:25 AM UTC (9h 14m)resolved
their latest update (Aug 8, 2026, 8:25 AM UTC): This incident has been resolved
Feature Flag Evaluation Errors (Statsig)Partial outage
Jul 9, 2026, 1:28 AM UTC to Jul 9, 2026, 2:36 AM UTC (1h 9m)resolved
their latest update (Jul 9, 2026, 2:36 AM UTC): 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…
Data ingestion delayedMinor incident
Jun 20, 2026, 3:22 AM UTC to Jun 20, 2026, 11:00 AM UTC (7h 38m)resolved
their latest update (Jun 20, 2026, 11:00 AM UTC): Warehouse native exposure forwarding has caught up.
Warehouse Native Pulse results delayed for customers with IP allowlists configuredMinor incident
Jun 16, 2026, 8:00 PM UTC to Jun 16, 2026, 8:00 PM UTC (0 min)resolved
their latest update (Jun 16, 2026, 8:00 PM UTC): 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.
Statsig Console temporarily downMajor outage
May 26, 2026, 6:01 PM UTC to May 26, 2026, 6:25 PM UTC (24 min)resolved
their latest update (May 26, 2026, 6:25 PM UTC): Resolved.
Config Propagation Delay and Increased Error Rates for Console APIPartial outage
May 2, 2026, 1:01 AM UTC to May 2, 2026, 3:15 AM UTC (2h 14m)resolved
their latest update (May 2, 2026, 3:15 AM UTC): Resolved.
Elevated 401 unauthorized from statsigcdnPartial outage
Apr 17, 2026, 12:25 AM UTC to Apr 17, 2026, 12:37 AM UTC (12 min)resolved
their latest update (Apr 17, 2026, 12:37 AM UTC): Resolved.
Apr 13, 2026, 5:33 PM UTC to Apr 13, 2026, 5:39 PM UTC (6 min)resolved
their latest update (Apr 13, 2026, 5:39 PM UTC): Resolved.
Showing the 10 most recent of 50 incidents Statsig has declared in the history we hold.
These entries are Statsig's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Statsig's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.