Skip to content

Outage tracker / Statsig / In the US

Is Statsig down in the US?

Vendor reports no incidentWhat Statsig reports

Statsig reports no incident on its status page.

As of the last successful poll, 2026-11-05 21:25 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 passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Statsig at Nov 5, 2026, 9:26 PM UTC.

Over the last 24 hours we completed 251 checks from Ashburn and San Jose and 251 answered cleanly, 100.00% availability.

Of the 2 other regions we check Statsig from, all 2 read checks passing right now.

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

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

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

What our Ashburn and San Jose probes measured

AshburnChecks passing141 checks in 24h, 100.00%
San JoseChecks passing110 checks in 24h, 100.00%

Last checked Nov 5, 2026, 9:26 PM UTC.

Statsig from Ashburn and San Jose over the last 30 days

Over the last 30 days, Statsig answered our Ashburn probe in 1,040 ms on average, and 1 check in 20 took longer than 1,436 ms.

Over the last 30 days, Statsig answered our San Jose probe in 1,201 ms on average, and 1 check in 20 took longer than 1,754 ms.

Ranked by average response time across the 4 cities we check Statsig from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 820 ms and Tokyo slowest at 1,515 ms.

From Ashburn and San Jose we ran 827 checks of Statsig in 4 days, and 827 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Statsig was slowest around 4 PM, at 1,225 ms on average over the last 14 days, and quickest around 9 AM, at 862 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5226100.00%1,121 ms
Wed, Nov 4251100.00%1,072 ms
Tue, Nov 3246100.00%1,155 ms
Mon, Nov 2104100.00%1,071 ms

Statsig outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Statsig outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Statsig from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 97 checks
TokyoChecks passing100.00% of 60 checks

Other countries we check Statsig from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Statsig's public endpoints. They are not user reports, and they are not Statsig's own status page.

See Statsig's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Statsig has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

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