Is Statsig Down?

No — Statsig is up

Reachable from all 8 checked regions

Average response time: 414ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.statsig.com

Statsig uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

585ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

413ms

DNS 0ms TCP 5ms TLS 9ms TTFB 411ms

arn

892ms

DNS 0ms TCP 6ms TLS 10ms TTFB 890ms

bom

527ms

DNS 0ms TCP 1ms TLS 6ms TTFB 526ms

cdg

366ms

DNS 0ms TCP 1ms TLS 8ms TTFB 364ms

dfw

206ms

DNS 0ms TCP 2ms TLS 7ms TTFB 205ms

sin

447ms

DNS 0ms TCP 2ms TLS 8ms TTFB 445ms

sjc

204ms

DNS 0ms TCP 11ms TLS 15ms TTFB 202ms

syd

363ms

DNS 0ms TCP 1ms TLS 6ms TTFB 361ms

yyz

341ms

DNS 0ms TCP 1ms TLS 5ms TTFB 339ms

What Statsig does

Statsig combines feature flags, experimentation, product analytics, session replay and web analytics in one platform. Client and server SDKs pull configuration from its Config Delivery API and send usage back through the Log Event API, so a Statsig fault reaches production applications rather than staying inside a dashboard. Customers include OpenAI, Brex and Notion.

What an outage looks like

Feature gates and experiments fall back to default values, so a released feature can silently disappear for users while your application logs nothing unusual. Events queue in the SDK and are dropped once the buffer fills, leaving gaps in metrics and skewing any experiment running at the time. The console may be unreachable separately, which stops changes but not delivery.

What to do about it

Read status.statsig.com, which separates Console, Config Delivery API and Log Event API, and reports Config Delivery per region across US West, US East, Europe West and Asia Southeast. Config Delivery is the line that affects your users; Console only affects your team. Do not ship a code change to work around missing flags until you know which component failed, since defaults return on their own.

Is it down for everyone, or just you?

If this page says Statsig is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Statsig outage FAQ

What happens to my feature flags when Statsig is down?

SDKs fall back to the default values compiled into your application rather than erroring, so nothing breaks visibly and a feature you had enabled can turn off for everyone. Server SDKs that have already fetched a config set usually keep serving it from memory, which means the impact often lands on newly started instances first rather than on the whole fleet at once.

Is Statsig down for everyone or just my region?

Config Delivery is reported per region, covering US West 1, US East 1, US East 5, Europe West 1 and Asia Southeast 1, so an incident is frequently confined to one of them and your users elsewhere are unaffected. Check the region your traffic is served from rather than the overall banner, which aggregates every region and every product line.

Will I lose experiment data during a Statsig outage?

Events buffer in the SDK and are dropped once that buffer fills, so a long incident leaves a hole in your metrics. The bigger problem is interpretation: an experiment that ran through an outage has a window where exposures and conversions are undercounted, and reading the result as clean can send you the wrong way. Compare the incident window against your analysis dates.

Does a Statsig console outage stop flags from working?

No. Console and Config Delivery API are separate components. When only the Console is affected, your team cannot change gates, view results or ship experiment updates, but the values already published keep being delivered to your applications normally. It is the reverse case, Config Delivery degraded while the Console works, that reaches your users.

How we measure this

We request Statsig's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Statsig publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Statsig goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required