Skip to content

Outage tracker / Statsig

Is Statsig down?

Short linkrlup.io/down/statsig

I'm having a problem

Vendor reports no incidentWhat Statsig reports

Statsig reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:39 UTC.

Statsig's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Statsig pass from all 4 regions we check.

As of Nov 5, 2026, 3:41 PM UTC, RealUptime's checks of Statsig passed in all 4 regions that returned a reading.

Front-door checks

our check readinglive · checked Nov 5, 2026, 3:41 PM UTC
US-East917 msChecks passing
US-West1186 msChecks passing
Europe738 msChecks passing
Asia-Pacific2046 msChecks passing
their status pagetheir claim, not our reading

Statsig reports: All systems operational (“All Systems Operational”)

from Statsig's own status page, checked Nov 5, 2026, 3:33 PM UTC
Statsig's own status page shows no incident, and our checks of Statsig pass right now.

Statsig's own component breakdown, as they publish it

  • ConsoleOperational
  • US West 1Operational
  • US East 1Operational
  • Log Event APIOperational
  • US East 5Operational
  • Console APIOperational
  • Europe West 1Operational
  • Asia Southeast 1Operational
  • Experiment Results (Cloud)Operational
  • Experiment Results (Warehouse Native)Operational
  • Event Forwarding Pipeline (Warehouse Native)Operational
  • Marketing SiteOperational
  • DocsOperational

These are Statsig's components, named and scored by Statsig. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Statsig's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Statsig response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Statsig

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Statsig. It cannot diagnose Statsig's own systems.

Email me when Statsig reports an incident on its status page, and again when it reports it resolved.

Get an email when Statsig reports an incident

Email me when Statsig reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Statsig's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 917msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Statsig normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1186msstatus code: 200checked: Nov 5, 2026, 3:30 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Statsig normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionStatsig is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionStatsig is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionStatsig is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 738msstatus code: 200checked: Nov 5, 2026, 3:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Statsig normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionStatsig is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2046msstatus code: 200checked: Nov 5, 2026, 3:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Statsig normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionStatsig is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionStatsig is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Statsig, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Statsig yet, which is not evidence that nothing is wrong.

Recent probe events

Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers, 65h 37mdeclared on their status page2026-08-28
Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) Customers, 1mdeclared on their status page2026-08-26
Warehouse Native accounts may be experiencing export delays for data from Aug 6, 9h 14mdeclared on their status page2026-08-07
Feature Flag Evaluation Errors (Statsig), 1h 9mdeclared on their status page2026-07-09
Data ingestion delayed, 7h 38mdeclared on their status page2026-06-20
Warehouse Native Pulse results delayed for customers with IP allowlists configured, 1mdeclared on their status page2026-06-16
Statsig Console temporarily down, 24mdeclared on their status page2026-05-26
Config Propagation Delay and Increased Error Rates for Console API, 2h 14mdeclared on their status page2026-05-02

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Statsig since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Statsig covering any window you pick, with our check readings and Statsig's own claim at the time, side by side.

Full check history for Statsig: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Statsig uptime by RealUptime's checksLive, from this page's own readings.
[![Statsig uptime by RealUptime's checks](https://realuptime.io/outages/statsig/badge.svg?days=30)](https://realuptime.io/outages/statsig)
<a href="https://realuptime.io/outages/statsig"><img src="https://realuptime.io/outages/statsig/badge.svg?days=30" alt="Statsig uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Statsig down?", https://realuptime.io/outages/statsig. The readings change with every check, so give the date you read them.

What we check

primary
https://statsig.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: statsig.com

RealUptime is not affiliated with Statsig; the name identifies what we checked, and nothing here speaks for Statsig's own team. We send a single web request to Statsig from 4 regions on our own schedule and time the response. We do not see inside Statsig's systems, do not use an account or real transaction, and are not the same signal Statsig's own team has access to. Treat this as one external data point, not a verdict. What we check for Statsig is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Statsig operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1254 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts