outages.live
Live

Statsig

Statsig is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Statsig status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Statsig since . The days before that show only what Statsig published.

Incidents in 90 days

2

Days with an incident

6

Median duration

37 h 25 min

Longest incident

3 days

Components

13
Console Operational
90 days agoNo incidentsToday
Log Event API Operational
90 days agoNo incidentsToday
Console API Operational
90 days agoNo incidentsToday
Experiment Results (Cloud) Operational
90 days agoNo incidentsToday
Experiment Results (Warehouse Native) Operational
90 days agoNo incidentsToday
Event Forwarding Pipeline (Warehouse Native) Operational
90 days ago6 days with an incidentToday
Marketing Site Operational
90 days agoNo incidentsToday
Docs Operational
90 days agoNo incidentsToday

Config Delivery API

US West 1 Operational
90 days agoNo incidentsToday
US East 1 Operational
90 days agoNo incidentsToday
US East 5 Operational
90 days agoNo incidentsToday
Europe West 1 Operational
90 days agoNo incidentsToday
Asia Southeast 1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Aug 28, 2026

Duration3 days to Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) CustomersDegraded

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!

Aug 7, 2026

Duration9 h 14 min to Warehouse Native accounts may be experiencing export delays for data from Aug 6Degraded

This incident has been resolved

Follow Statsig

Your coding agent knows when Statsig is down, and tells you when a failure is theirs, not yours. You can also get Statsig incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "statsig" and tell me if Statsig has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=statsig
Slack
/feed subscribe https://outages.cc/feed.xml?providers=statsig

Go from tracking outages to fixing production issues with Polylane.

Try Polylane