User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
statsig.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests statsig.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 712 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 663 ms | 0 |
| 03:30 | 0 | 0.0 | 205 ms | 0 |
| 03:45 | 0 | 0.0 | 321 ms | 0 |
| 04:00 | 0 | 0.0 | 228 ms | 0 |
| 04:15 | 0 | 0.0 | 149 ms | 0 |
| 04:30 | 0 | 0.0 | 390 ms | 0 |
| 04:45 | 0 | 0.0 | 148 ms | 0 |
| 05:00 | 0 | 0.0 | 293 ms | 0 |
| 05:15 | 0 | 0.0 | 613 ms | 0 |
| 05:30 | 0 | 0.0 | 411 ms | 0 |
| 05:45 | 0 | 0.0 | 130 ms | 0 |
| 06:00 | 0 | 0.0 | 134 ms | 0 |
| 06:15 | 0 | 0.0 | 283 ms | 0 |
| 06:30 | 0 | 0.0 | 300 ms | 0 |
| 06:45 | 0 | 0.0 | 270 ms | 0 |
| 07:00 | 0 | 0.0 | 228 ms | 0 |
| 07:15 | 0 | 0.0 | 166 ms | 0 |
| 07:30 | 0 | 0.0 | 348 ms | 0 |
| 07:45 | 0 | 0.0 | 269 ms | 0 |
| 08:00 | 0 | 0.0 | 263 ms | 0 |
| 08:15 | 0 | 0.0 | 124 ms | 0 |
| 08:30 | 0 | 0.0 | 453 ms | 0 |
| 08:45 | 0 | 0.0 | 269 ms | 0 |
| 09:00 | 0 | 0.0 | 293 ms | 0 |
| 09:15 | 0 | 0.0 | 321 ms | 0 |
| 09:30 | 0 | 0.0 | 285 ms | 0 |
| 09:45 | 0 | 0.0 | 143 ms | 0 |
| 10:00 | 0 | 0.0 | 517 ms | 0 |
| 10:15 | 0 | 0.0 | 187 ms | 0 |
| 10:30 | 0 | 0.0 | 244 ms | 0 |
| 10:45 | 0 | 0.0 | 252 ms | 0 |
| 11:00 | 0 | 0.0 | 129 ms | 0 |
| 11:15 | 0 | 0.0 | 327 ms | 0 |
| 11:30 | 0 | 0.0 | 160 ms | 0 |
| 11:45 | 0 | 0.0 | 391 ms | 0 |
| 12:00 | 0 | 0.0 | 147 ms | 0 |
| 12:15 | 0 | 0.0 | 384 ms | 0 |
| 12:30 | 0 | 0.0 | 169 ms | 0 |
| 12:45 | 0 | 0.0 | 134 ms | 0 |
| 13:00 | 0 | 0.0 | 500 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Statsig yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Statsig goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Statsig alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Statsig is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Statsig's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.