Statsig logo

Is Statsig Down?

AnalyticsLive status, outages, and incident history

No. Statsig is up right now.

Every monitored Statsig system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Statsig breaks

Statsig is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Statsig status page
How we know: the official Statsig status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Statsig Status Summary

As of 22:52 UTC on 9 November 2026, Statsig is operational. PulsAPI checked Statsig's official status page and found 13 of 13 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Statsig, counting degraded performance as up. The latest incident, "Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers", was on Aug 28, 2026 and lasted 65h 36m.

Cite as: PulsAPI, “Statsig status”, checked 9 November 2026, 22:52 UTC. https://www.pulsapi.com/services/statsig

Statsig Component Status

The main Statsig systems on this page. All 13 are operational right now.

13operational
Config Delivery API » Asia Southeast 1
Operational
Config Delivery API » Europe West 1
Operational
Config Delivery API » US East 1
Operational

10 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Config Delivery API » US East 5, Config Delivery API » US West 1, Console, Console API, Docs, Event Forwarding Pipeline, Experiment Results, Log Event API, Marketing Site.

See all of them free

Component statuses may change independently during partial outages.

Recent Statsig Outages & Incidents

Incident history from the official Statsig status page, including resolution updates.

Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) CustomersResolved Aug 28, 2026 · 65h 36mResolved

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.

Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) CustomersResolved Aug 27, 2026Resolved

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

Statsig Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Statsig incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history90 days observed
Aug 12100.00% average · 4 days with incidentsNov 9

Going further back: Statsig uptime by month and every recorded Statsig outage.

Live Statsig Outage Reports

Problems reported by engineers using Statsig. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Statsig problems reported yet.

Something wrong with Statsig on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Statsig

Statsig exposes 14 monitored components on its status page at status.statsig.com — Console, US West 1 and Config Delivery API among them. Follow Statsig downtime, degraded performance and resolved incidents here, with uptime history alongside your other analytics services.

Over the past 30 days, PulsAPI has measured Statsig uptime at 100.00%. Response times, incident history, and SLA tracking for Statsig are available on the PulsAPI dashboard.

Statsig Status FAQ

Is Statsig down right now?

The verdict at the top of this page comes from the latest poll of the official Statsig status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Statsig is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Statsig recovers.

How do I check Statsig uptime history?

PulsAPI tracks Statsig uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Statsig changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Statsig outages?

PulsAPI reads the official Statsig status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Statsig components?

Yes. PulsAPI monitors 13 individual Statsig components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Statsig goes down?

Yes. Create a free account and subscribe to Statsig: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Statsig to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Statsig problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Statsig?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Statsig plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Statsig with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services