outages.live
Live
StatsigIncident ·

Warehouse Native accounts may be experiencing export delays for data from Aug 6

ResolvedOfficial update

This incident has been resolved

The latest update from Statsig.

State

Resolved

Started

Lasted

9 h 14 min

Worst impact

Degraded

Timeline

4 updates
23:1001:2903:4706:0608:25
DegradedUpdate postedTimes in UTC

Monitoring

9 h 14 min 100%

Updates

Times in UTC

As posted by Statsig

Resolved

This incident has been resolved

Monitoring

Thank you for your patience. The main query-intensive jobs are through now, but it also took quite a bit longer than before. Catch up for subsequent jobs may therefore take up to 3am PT to complete. Our sincere apologies for the delay and we will continue to share updates as we monitor the job completion.

Monitoring

We are still making progress on re-running the exports. We should start to see some exports completing but the expected completion time for the full system to rerun has extended to 9pm PT. We will continue to keep you updated and aim to have the next update at 9pm PT! To clarify: 1. This only impacts customers who use Statsig warehouse native. If you are on Statsig cloud, you can ignore this status page. 2. For WHN customers, once we finish rerunning the final jobs, Statsig will automatically take care of refreshing the data for all experiments that are configured to incrementally refresh metrics.

Monitoring

This issue only impacts customers on Warehouse Native on the echidna pipeline. Around 11 am PT, we have identified that WHN accounts will have event and exposure export delays from August 6. No data is lost as the job rebuilds the full day from source so there will be no gaps once the post-revert run lands. Everything through August 5 is intact. Around 1pm PT, we have implemented a fix that should have mitigated this issue. We expect exports to complete around 7pm PT.

Affected components

1
Event Forwarding Pipeline (Warehouse Native)

Statsig in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

6

Median duration

37 h 25 min

This incident

75% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days
median 37 h 25 min
90 days agoToday

Other Statsig incidents

All incidents

Statsig·Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers

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!

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane