Statsig Outage History
Statsig is up right nowPingoru has recorded 53 incidents for Statsig: 27 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| May 2026 | 4 | 3 of 744 (0%) |
| June 2026 | 3 | 128 of 720 (18%) |
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 3 | 75 of 744 (10%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 115 (0%) |
Incidents, newest first
Minor August 28, 2026 Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers 2d 17h Event Forwarding Pipeline (Warehouse Native)
Started Aug 28, 2026, 10:40 PM UTC· resolved Aug 31, 2026, 04:17 PM UTC
- monitoring Aug 28, 2026, 10:40 PM UTC
Follow up to the Aug 26 issue impacting Warehouse-Native (WHN) customers: https://status.statsig.com/incidents/prtl9797v2y0 We recently identified a sub-issue affecting the export of exposure data for certain Feature Gates, specifically those gates without an associated metric, with 100%/0% rollout etc where no analytics is turned on. For these Feature Gates, the exposures for August 25 onward may still be missing or incomplete in your warehouse. Experiment exposures, live event ingestion, and the Exposure Stream are unaffected. Underlying exposure data has not been lost and is being backfilled. We have identified the root cause, deployed a fix, and are actively backfilling affected data for impacted customers. No action is needed and no reload is needed. Customers can expect/monitor those gates' exposure landed into their warehouse in the next two days.
- resolved Aug 31, 2026, 04:17 PM UTC
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!
Notice August 25, 2026 Delayed Experiment & Feature Gate Results for Warehouse-Native (WHN) Customers 4h 23m
Started Aug 25, 2026, 09:30 AM UTC· resolved Aug 25, 2026, 01:53 PM UTC
- resolved Aug 26, 2026, 09:30 AM UTC
-- Only WHN customers are impacted -- Around 2026-08-26 2:30 PT (16:30 UTC), we were experiencing a delay in processing experiment and feature gate exposure data for Warehouse-Native (WHN) customers. As a result, experiment and feature gate results may show fewer participants than expected for August 25–26, and cumulative metric totals from August 25 onward may appear understated. Live event ingestion and the Exposure Stream are unaffected. Data is delayed, not lost. As of 2026-08-27, 06:53 PT, our team has identified the root cause and actively worked to backfill affected data and restored normal processing. The underlying data has now been reprocessed and delivered. - If your experiments are on a scheduled reload, no action is needed — the next scheduled run recalculates the affected dates automatically and restores the missing participants. Results should be complete after that run. - A reload is required in two cases. If an experiment/gate has already been stopped or concluded, its results will not update on their own and need a full reload. If you reload manually rather than on a schedule, please run a reload before 28 August so the recalculation covers both affected dates; after that a full reload is needed instead of an incremental one.
Minor August 7, 2026 Warehouse Native accounts may be experiencing export delays for data from Aug 6 9h 14m Event Forwarding Pipeline (Warehouse Native)
Started Aug 07, 2026, 11:10 PM UTC· resolved Aug 08, 2026, 08:25 AM UTC
- monitoring Aug 07, 2026, 11:10 PM UTC
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.
- monitoring Aug 08, 2026, 12:57 AM UTC
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 Aug 08, 2026, 04:00 AM UTC
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.
- resolved Aug 08, 2026, 08:25 AM UTC
This incident has been resolved
Major July 9, 2026 Feature Flag Evaluation Errors (Statsig) 1h 8m US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Jul 09, 2026, 01:28 AM UTC· resolved Jul 09, 2026, 02:36 AM UTC
- identified Jul 09, 2026, 01:28 AM UTC
Since approximately 1:56 PM PT on July 8 (20:56 UTC on July 8), customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. Specifically, launched Gates may have returned false instead of their expected default value. Our team identified the root cause as a recent code change and started a rollback of the affected services. We were actively working to confirm that evaluations returned by the V2 Config Delivery API were again showing expected defaults for launched Gates. V1 consumers were not affected. At the time of this update, no immediate customer action was required. We would provide the next update as more information became available.
- identified Jul 09, 2026, 01:29 AM UTC
We are continuing to work on a fix for this issue.
- identified Jul 09, 2026, 01:35 AM UTC
We are continuing to work on a fix for this issue.
- identified Jul 09, 2026, 01:39 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Jul 09, 2026, 02:15 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 09, 2026, 02:36 AM UTC
Between approximately 20:56 UTC on July 8 and 01:40 UTC on July 9, customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. During this window, launched Gates could return false instead of their expected default. V1 consumers were not affected. We identified the root cause as a recent change to config-spec generation. We rolled back the affected services across all regions and regenerated config payloads. We have verified that launched Gates are again returning their expected defaults, and all Config Delivery API components are now operational. No action is required to restore correct evaluation going forward. However, if your systems persisted data or took actions based on evaluations returned by the V2 Config Delivery API during the impact window, we recommend reviewing and reconciling that downstream data, as affected launched Gates may have returned false during that time.
Minor June 20, 2026 Data ingestion delayed 7h 37m Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native)
Started Jun 20, 2026, 03:22 AM UTC· resolved Jun 20, 2026, 11:00 AM UTC
- monitoring Jun 20, 2026, 03:22 AM UTC
We have identified an issue from a recent change impacting BigQuery connectivity since 4:30pm PST. No data has been lost. We have rolled back the change and data ingestion is catching up. Experiment results for some customers may be delayed.
- monitoring Jun 20, 2026, 05:36 AM UTC
Data ingestion has caught up and is operating normally. We are continuing to monitor warehouse native exposure forwarding delay.
- resolved Jun 20, 2026, 11:00 AM UTC
Warehouse native exposure forwarding has caught up.
Major June 11, 2026 docs: major outage 41m docs
Started Jun 11, 2026, 10:15 PM UTC· resolved Jun 11, 2026, 10:56 PM UTC
No vendor updates were posted for this incident.
Minor June 11, 2026 Warehouse Native Pulse results delayed for customers with IP allowlists configured 5d
Started Jun 11, 2026, 08:00 PM UTC· resolved Jun 16, 2026, 08:00 PM UTC
- resolved Jun 16, 2026, 08:00 PM UTC
A recent infra change spun up WHN compute with public IPs instead of routing through our published NAT ranges. Pulse traffic briefly left from an IP address which isn't in our published list. We've fixed routing; egress is back on the published IPs. No allowlist change needed.
Critical May 26, 2026 Statsig Console temporarily down 24m Console
Started May 26, 2026, 06:01 PM UTC· resolved May 26, 2026, 06:25 PM UTC
- investigating May 26, 2026, 06:01 PM UTC
console.statsig.com was temporarily down but recovered shortly. No flag checks or SDKs calls were affected. Mitigated: 05/26/2026 11:25:00 GMT-0700 (Pacific Daylight Time) We have determined the root cause and will work to prevent this.
- resolved May 26, 2026, 06:25 PM UTC
Resolved.
Major May 26, 2026 console: major outage 24m console
Started May 26, 2026, 11:01 AM UTC· resolved May 26, 2026, 11:25 AM UTC
No vendor updates were posted for this incident.
Major May 5, 2026 docs: major outage 25m docs
Started May 05, 2026, 08:35 PM UTC· resolved May 05, 2026, 09:00 PM UTC
No vendor updates were posted for this incident.
Major May 2, 2026 Config Propagation Delay and Increased Error Rates for Console API 2h 14m US West 1, US East 1, US East 5, Europe West 1 and 2 more
Started May 02, 2026, 01:01 AM UTC· resolved May 02, 2026, 03:15 AM UTC
- investigating May 02, 2026, 01:01 AM UTC
We are investigating elevated error rates affecting the Console API, along with delayed propagation for some configuration changes. Our team has identified the issue and is actively working to restore normal service. Mitigated: 05/01/2026 20:15:00 GMT-0700 (Pacific Daylight Time)
- resolved May 02, 2026, 03:15 AM UTC
Resolved.
Major April 17, 2026 Elevated 401 unauthorized from statsigcdn 12m US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Apr 17, 2026, 12:25 AM UTC· resolved Apr 17, 2026, 12:37 AM UTC
- investigating Apr 17, 2026, 12:25 AM UTC
We are investigating an elevated number of 401 unauthorized returns from api.statsigcdn.com Mitigated: 04/16/2026 17:37:00 GMT-0700 (Pacific Daylight Time): We have implemented a fix and are in recovery
- resolved Apr 17, 2026, 12:37 AM UTC
Resolved.
Major April 13, 2026 Increased error rates affecting Console APIs 6m Console API
Started Apr 13, 2026, 05:33 PM UTC· resolved Apr 13, 2026, 05:39 PM UTC
- investigating Apr 13, 2026, 05:33 PM UTC
**04/13/2026 10:33 PDT Investigating**: We are addressing increased 5XX error rates impacting our console APIs. Investigation and fix is underway **04/13/2026 10:39 PDT Mitigated**: 5XX errors have been resolved and impact was limited to few customers. Config propagation and console APIs are healthy.
- resolved Apr 13, 2026, 05:39 PM UTC
Resolved.
Minor March 30, 2026 Statsig experiencing propagation delays 1h 50m US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Mar 30, 2026, 08:20 PM UTC· resolved Mar 30, 2026, 10:10 PM UTC
- investigating Mar 30, 2026, 08:20 PM UTC
From approximately 1:20PM PST to 3:10PM PST, we identified a code path that was creating write pressure on our redis cache which caused propagation to slow down. Resolution was resolved by mitigating the write pressure, and the team is following up on preventative measures to address the root cause. Systems are fully recovered at this point. Mitigated: 03/30/2026 14:19:00 GMT-0700 (Pacific Daylight Time)
- resolved Mar 30, 2026, 10:10 PM UTC
Resolved.
Major March 18, 2026 Regional Issue for Statsig Console 40m Console, Console API
Started Mar 18, 2026, 09:25 PM UTC· resolved Mar 18, 2026, 10:05 PM UTC
- investigating Mar 18, 2026, 09:25 PM UTC
**03/18/2026 14:25 PDT Investigating**: We are investigating reports of limited access to the Statsig Console for some customers. SDK and API usage remain unaffected, as values, exposures, and events continue to be processed. **03/18/2026 14:45 PDT Update**: Statsig Console has been repaired and is back online. Console API is still recovering **03/18/2026 15:05 PDT Update - Fully Recovered**: All issues have been mitigated with Statsig Console and CAPI recovered.
- resolved Mar 18, 2026, 10:05 PM UTC
Resolved.
Major March 18, 2026 Client SDK Success Rate in Southeast Asia 1h 3m Asia Southeast 1
Started Mar 18, 2026, 01:50 AM UTC· resolved Mar 18, 2026, 02:53 AM UTC
- investigating Mar 18, 2026, 01:50 AM UTC
We are seeing degraded success rate in our southeast asia region for client SDK initialization starting at around 6:50PM. The team has identified the root cause and is working on recovering the region now. Update: 7:51PM PST -- The team expects full recovery within a few minutes. Update: 7:57PM PST -- Systems are fully recovered as of 7:53 PM PST.
- resolved Mar 18, 2026, 02:53 AM UTC
Resolved.
Minor March 11, 2026 Delayed Configuration Propagation 10h 13m US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Mar 11, 2026, 10:38 AM UTC· resolved Mar 11, 2026, 08:51 PM UTC
- investigating Mar 11, 2026, 10:38 AM UTC
We are currently seeing issues with config propagation for server SDKs. The team is currently investigating and will provide updates soon. Update: 12:37PM PST The team has identified what the root cause is and is working on getting a fix deployed now. We are currently aiming for recovery around 1PM. Update: 1:14PM PST Most companies should see configuration propagating again, we are continuing to work on full recovery. Delay should at most be a few minutes at this point. Update: 1:51PM PST We continue to see config propagation hold at a steady state, the team is working on fast follow ups for prevention to ensure we can confidently mark the incident as resolved.
- resolved Mar 11, 2026, 08:51 PM UTC
Resolved.
Critical February 25, 2026 Statsig Console Availability 5m Console
Started Feb 25, 2026, 07:11 PM UTC· resolved Feb 25, 2026, 07:16 PM UTC
- investigating Feb 25, 2026, 07:11 PM UTC
console.statsig.com was unavailable from 11:11AM to 11:16AM PST. The team is currently investigating to understand what the rootcause was. Functionality is fully restored and no further impact should be expected.
- resolved Feb 25, 2026, 07:16 PM UTC
Resolved.
Minor January 27, 2026 Elevated Latency for Cloudflare CDN 4d 5h US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Jan 27, 2026, 01:44 AM UTC· resolved Jan 31, 2026, 07:25 AM UTC
- investigating Jan 27, 2026, 01:44 AM UTC
We are currently seeing elevated latency for server SDK configuration payloads at our Cloudflare CDN due to congestion at their edge hosts. We are working with them to mitigate the issue. Update: 01/30/2026 11:49AM PST We have seen some customers seeing latency improve with mitigated congestion. We're still working with Cloudflare to full resolve the issue for everyone. Update: 01/30/2026 11:25PM PST Latency has been restored to healthy, baseline levels.
- resolved Jan 31, 2026, 07:25 AM UTC
Resolved.
Minor January 26, 2026 Investigating Config Propagation 1m US West 1, US East 1, US East 5, Event Forwarding Pipeline (Warehouse Native)
Started Jan 26, 2026, 05:34 PM UTC· resolved Jan 26, 2026, 05:35 PM UTC
- investigating Jan 26, 2026, 05:34 PM UTC
We are currently investigating an issue affecting config propagation in the us-east5, us-east1, us-west1 regions. Some customers may be experiencing service interruptions or degraded performance. Diagnostic events are also delayed in these regions. Our Infrastructure team is actively working to identify the root cause and restore normal operation.
- resolved Jan 26, 2026, 05:35 PM UTC
Resolved.
Major January 24, 2026 Issues for Server SDKs in US-EAST and US-WEST 1h 23m US West 1, US East 1
Started Jan 24, 2026, 12:00 AM UTC· resolved Jan 24, 2026, 01:23 AM UTC
- investigating Jan 24, 2026, 12:00 AM UTC
We’ve identified increased error rates for Server SDKs initializing/syncing updates in the US-EAST and US-WEST regions starting around 16:00 PST. We are actively investigating the issue.
- resolved Jan 24, 2026, 01:23 AM UTC
Resolved.
Minor January 15, 2026 Topline Alerts Misfiring 1m
Started Jan 15, 2026, 11:30 PM UTC· resolved Jan 15, 2026, 11:31 PM UTC
- investigating Jan 15, 2026, 11:30 PM UTC
Around 3pm PST, there was a burst of topline alerts firing when their triggers were not met. This has been resolved.
- resolved Jan 15, 2026, 11:31 PM UTC
Resolved.
Major January 12, 2026 Success Rate drop for US East Region 1h 54m US East 1, Log Event API
Started Jan 12, 2026, 08:30 PM UTC· resolved Jan 12, 2026, 10:24 PM UTC
- investigating Jan 12, 2026, 08:30 PM UTC
At 12:30 PM PST we saw elevated error rates for both initialize and event logging traffic. We are investigating the issue. Mitigated: 01/12/2026 14:24:00 GMT-0800 (Pacific Standard Time)
- resolved Jan 12, 2026, 10:24 PM UTC
Resolved.
Minor December 11, 2025 Slack Integration Oversending 1h 38m
Started Dec 11, 2025, 07:52 PM UTC· resolved Dec 11, 2025, 09:30 PM UTC
- investigating Dec 11, 2025, 07:52 PM UTC
Customers with multiple Slack channels configured are receiving messages in all channels, instead of only those filtered to the individual channel. We are investigating the issue. Mitigated: 12/11/2025 1:30:00 GMT-0800 (Pacific Standard Time)
- resolved Dec 11, 2025, 09:30 PM UTC
Resolved.
Major November 18, 2025 11/18/2025 06:50:00 GMT-0800 (Pacific Standard Time) 1m US West 1, US East 1, US East 5, Europe West 1 and 1 more
Started Nov 18, 2025, 02:50 PM UTC· resolved Nov 18, 2025, 02:51 PM UTC
- investigating Nov 18, 2025, 02:50 PM UTC
We are seeing recovery on affected requests via cloudflare as of 6.42am PT. We will continue to monitor the health of our systems as we recover. Mitigated: 11/18/2025 05:34:00 GMT-0800 (Pacific Standard Time)
- resolved Nov 18, 2025, 02:51 PM UTC
Resolved.