Statsig

Affected: Event Forwarding Pipeline (Warehouse Native)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-28 22:40 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,...

2. resolved 2026-08-31 16:17 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!

Excerpts are shortened. Read the full incident on Statsig's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-08-26 09:30 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...

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Event Forwarding Pipeline (Warehouse Native)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-07 23:10 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...

2. monitoring 2026-08-08 00:57 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...

3. monitoring 2026-08-08 04:00 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...

4. resolved 2026-08-08 08:25 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-09 01:28 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...

2. identified 2026-07-09 01:29 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-07-09 01:35 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-07-09 01:39 UTC

   We are continuing to work on a fix for this issue.

5. monitoring 2026-07-09 02:15 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-07-09 02:36 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...

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native)

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-20 03:22 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.

2. monitoring 2026-06-20 05:36 UTC

   Data ingestion has caught up and is operating normally. We are continuing to monitor warehouse native exposure forwarding delay.

3. resolved 2026-06-20 11:00 UTC

   Warehouse native exposure forwarding has caught up.

Excerpts are shortened. Read the full incident on Statsig's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-16 20:00 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.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 18:01 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.

2. resolved 2026-05-26 18:25 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Console API, Asia Southeast 1

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-02 01:01 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)

2. resolved 2026-05-02 03:15 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-17 00:25 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

2. resolved 2026-04-17 00:37 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-13 17:33 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...

2. resolved 2026-04-13 17:39 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-30 20:20 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...

2. resolved 2026-03-30 22:10 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console, Console API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-18 21:25 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...

2. resolved 2026-03-18 22:05 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Asia Southeast 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-18 01:50 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...

2. resolved 2026-03-18 02:53 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-11 10:38 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...

2. resolved 2026-03-11 20:51 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-25 19:11 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.

2. resolved 2026-02-25 19:16 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-01-27 01:44 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...

2. resolved 2026-01-31 07:25 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Event Forwarding Pipeline (Warehouse Native)

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-26 17:34 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...

2. resolved 2026-01-26 17:35 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-24 00:00 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.

2. resolved 2026-01-24 01:23 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-15 23:30 UTC

   Around 3pm PST, there was a burst of topline alerts firing when their triggers were not met. This has been resolved.

2. resolved 2026-01-15 23:31 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US East 1, Log Event API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-12 20:30 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)

2. resolved 2026-01-12 22:24 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-11 19:52 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)

2. resolved 2025-12-11 21:30 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-18 14:50 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)

2. resolved 2025-11-18 14:51 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 13:00 UTC

   We are currently experiencing elevated 5xx errors from our CDN provider. You can track the upstream issue at the provider’s status page: https://www.cloudflarestatus.com/ This affects CDN endpoints used by all server SDKs to download configuration updates. SDKs using...

2. resolved 2025-11-18 14:42 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Log Event API, Europe West 1, Asia Southeast 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-07 00:33 UTC

   The engineering team is currently investigating. We are seeing high unavailability from 4:33PM PST, but mostly recovered by 4:38PM PST. Client SDK Initialization failed to initialize during this time period for a majority of requests, and event logging calls failed as well....

2. resolved 2025-11-07 00:38 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1, Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-31 21:52 UTC

   There were propagation delays across multiple regions caused by a bad config pushed earlier today, impacting the SDK and CDN. Additionally, there were also slower than real time ingestion speeds which affects data realtimeness in console surfaces such as diagnostics and...

2. resolved 2025-10-31 21:53 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-30 18:56 UTC

   Starting at 11:56AM PST, a networking configuration change caused a partial outage for SDK initialization APIs (/v1/initialize, /v1/download_config_specs, /v2/download_config_specs) in all clusters. The team is in the process of fast reverting this change, which will restore...

2. resolved 2025-10-30 19:20 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, Console API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-23 00:10 UTC

   Starting at 5:10PM PST, a networking change was made which caused an outage of all endpoints going to our US-West region to route to the incorrect backend causing exceptions, such as filter abort/RBAC denied. The team has addressed the networking change, and the US-West region...

2. resolved 2025-10-23 00:35 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-10 16:43 UTC

   From approximately 9:43 AM PST to 9:52 AM PST, we identified some stability issues in our initialization APIs which may impact initialization during that time. The team is investigating to understand and rootcause the incident. Mitigated: 10/10/2025 09:51:00 GMT-0700 (Pacific...

2. resolved 2025-10-10 16:52 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Log Event API, Europe West 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-09 15:30 UTC

   At 08:30:00 GMT-0700, we saw a drop in success rate metrics for approximately 5 minutes in our Europe North region, that has now resolved. The team is investigating further.

2. resolved 2025-10-09 15:35 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-03 19:02 UTC

   A new column was introduced to the first-exposures API Export, affecting some companies using the /console/v1/reports endpoint for dates 2025-09-30 - 2025-10-02. Reports for these days have been regenerated. Mitigated: 10/03/2025 12:02:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-10-03 19:03 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Experiment Results (Cloud)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-02 17:20 UTC

   We are aware of an issue where some feature gates may have a delay in Pulse results being available. The team is currently investigating and working on mitigating the issue. Further updates will be shared here. Mitigated: 10/03/2025 03:00:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-10-03 10:00 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Console API, Event Forwarding Pipeline (Warehouse Native)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-19 08:00 UTC

   There was a configuration issue affecting some companies that use the Console API and the RevenueCat, Amplitude, and Rudderstack incoming integrations, causing some requests to be processed incorrectly. This issue has been mitigated. Events sent to the above integrations will be...

2. resolved 2025-09-22 18:31 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-15 17:03 UTC

   There was a regression affecting propagation times for some companies in all configuration types, leading to outdated evaluations through server SDKs. This has now been mitigated Mitigated: 09/15/2025 11:37:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-09-15 18:37 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Europe West 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-02 18:44 UTC

   The team identified elevated 5xx rates in our EU regions starting at around 11:44AM PST, this primarily impacting SDK initialization. The issue was fully resolved by approximately 12:34 PM PST. Mitigated: 09/02/2025 12:34:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-09-02 19:34 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Log Event API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-25 18:20 UTC

   There was a drop in success rate between 11:20am PST and 12:00pm PST for the /api/v1/log_event and /api/v1/rgstr endpoints. This has now been mitigated. Mitigated: 08/25/2025 11:51:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-08-25 19:00 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-15 23:26 UTC

   **08/15/2025 17:05 PDT Mitigated**: Error rates have returned to their baseline **08/15/2025 16:26 PDT Investigating**: We are currently investigating an increase in errors for initialization for client SDKs

2. resolved 2025-08-16 00:05 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US East 5

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-06 11:46 UTC

   The team has identified a latency regression in our US East5 API Gateway that started at approximately 4:46am to 8:26am. The issue is now resolved.

2. resolved 2025-08-06 15:26 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-28 20:48 UTC

   The team has found the initial trigger to the incident and have now patched and addressed the issue. We are considering the incident fully mitigated at this point.

2. resolved 2025-07-28 20:49 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-28 19:15 UTC

   The team has placed a number of mitigations in place for prevention based on the symptoms we understand from the incident. We are continuing to gather information for the full understanding of the incident. Mitigated: 07/14/2025 09:40:00 GMT-0700 (Pacific Daylight Time)

2. resolved 2025-07-28 19:16 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, Log Event API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-28 14:45 UTC

   The team has been notified about elevated latency from approximately 7:45AM to 8:50AM PST in our US-West region. The incident is recovered at this point in time, however, the team is following up with a deeper investigation.

2. resolved 2025-07-28 15:50 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US East 1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-07-18 15:10 UTC

   At approximately, 8:10AM PST, we detected a growing rate of 5xx in our US East region. We have shifted traffic, and expect things to recover fully in a few minutes. Mitigated: 07/18/2025 08:21:00 GMT-0700 (Pacific Daylight Time): The traffic shift has completed and things should...

2. resolved 2025-07-18 15:21 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Log Event API, Europe West 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-07 20:05 UTC

   **07/07/2025 13:30 PDT Mitigated**: Starting at 1:05 PM PDT, we experienced a drop in API success rate in Europe North. We redirected all traffic to healthy regions to mitigate customer impact. No data loss occurred. **07/07/2025 13:05 PDT Investigating**: API success rates in...

2. resolved 2025-07-07 20:30 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Europe West 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-04 19:25 UTC

   **07/04/2025 12:28 PDT Mitigated**: We have mitigated the elevated 5xx error rates for client SDK initialization in the EU-West region. **07/04/2025 12:25 PDT Investigating**: Started observing elevated 5xx error rates for client SDK initialization in the EU-West region.

2. resolved 2025-07-04 19:28 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Log Event API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-06 18:53 UTC

   **06/06/2025 12:10 PDT Mitigated**: US East1 has been fully drained, and customers should see normal levels of 5xx again. **06/06/2025 12:01 PDT Investigating**: EU West has fully recovered, and traffic in US East is showing signs of improvement. **06/06/2025 11:53 PDT...

2. resolved 2025-06-06 19:10 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US East 1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-05 22:05 UTC

   **06/05/2025 15:30 PDT Mitigated**: Traffic has been rerouted from the affected cluster in East US to nearby regions. Configuration update propagation latency has stabilized. **06/05/2025 15:25 PDT Investigating**: Starting at 15:05 PDT, users in the East US region experienced...

2. resolved 2025-06-05 22:30 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-31 01:20 UTC

   **05/30/2025 19:30 PDT Mitigated**: Streaming data is continued towards full recovery. **05/30/2025 18:55 PDT Recovering**: The cause of the data delay has been addressed. Streaming data is now in the process of recovery. **05/30/2025 18:20 PDT Investigating**: Data delays are...

2. resolved 2025-05-31 02:30 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1, US East 1, US East 5, Europe West 1, Asia Southeast 1

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-06 17:45 UTC

   We were notified by alerts and the team has reverted the change that caused elevated errors from 10.45, which would have affected initializing client SDKs in some locations. [Update]: Issue was root caused and resolved at 11:02 AM PST. Rollout was gated off and impact was...

2. resolved 2025-05-06 18:02 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Experiment Results (Cloud)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-01 16:00 UTC

   **05/01/2025 12:20 PDT Mitigated**: All experimental results have landed. **05/01/2025 09:00 PDT Investigating**: There is an ongoing delay in the delivery of experiment results for some companies.

2. resolved 2025-05-01 19:20 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: US West 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-18 21:33 UTC

   **04/18/2025 15:33 PDT Mitigated**: The delay in propagation for all configuration types in the US West region has been mitigated. Normal operation has resumed. **04/18/2025 14:33 PDT Investigating**: We observed delayed propagation of all configuration types in the US West...

2. resolved 2025-04-18 22:33 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.

Affected: Asia Southeast 1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-17 01:00 UTC

   **04/16/2025 20:40 PDT Mitigated**: The sporadic propagation delays affecting updates to all configuration types in Southeast Asia were resolved. **04/16/2025 18:00 PDT Investigating**: We detected intermittent delays in the propagation of updates to all configuration types for...

2. resolved 2025-04-17 03:40 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Statsig's status page.