Statsig Outage History

Statsig is up right now

Pingoru has recorded 53 incidents for Statsig: 27 in the last 12 months and 3 in the last 90 days.

Source: status.statsig.com

53incidents recorded
27last 12 months
3last 90 days
12 hourstypical duration
Incidents per month
024MayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOctNov0%
Pingoru began tracking Statsig in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202643 of 744 (0%)
June 20263128 of 720 (18%)
July 202611 of 744 (0%)
August 2026375 of 744 (10%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 116 (0%)

Incidents, newest first

Major November 18, 2025 11/18/2025 05:00:00 GMT-0800 (Pacific Standard Time) 1h 42m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started Nov 18, 2025, 01:00 PM UTC· resolved Nov 18, 2025, 02:42 PM UTC

  1. investigating Nov 18, 2025, 01:00 PM 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 fallbackToStatsigAPI (where supported) or a local DataStore will continue operating, but may not receive the latest configuration changes until the CDN recovers.

  2. resolved Nov 18, 2025, 02:42 PM UTC

    Resolved.

Read the full incident report →

Critical November 7, 2025 Client SDK Initialization and Event Logging Unavailable for 5 minutes 5m US West 1, US East 1, US East 5, Log Event API and 2 more

Started Nov 07, 2025, 12:33 AM UTC· resolved Nov 07, 2025, 12:38 AM UTC

  1. investigating Nov 07, 2025, 12:33 AM 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. However, we expect that most events will be recoverable due to SDK level retries. Mitigated: 11/06/2025 16:40:00 GMT-0800 (Pacific Standard Time)

  2. resolved Nov 07, 2025, 12:38 AM UTC

    Resolved.

Read the full incident report →

Minor October 31, 2025 Data propagation delays 1m US West 1, US East 1, US East 5, Europe West 1 and 3 more

Started Oct 31, 2025, 09:52 PM UTC· resolved Oct 31, 2025, 09:53 PM UTC

  1. investigating Oct 31, 2025, 09:52 PM 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 dashboards. The team has identified the rootcause and system health has been restored.

  2. resolved Oct 31, 2025, 09:53 PM UTC

    Resolved.

Read the full incident report →

Major October 30, 2025 Degraded SDK initialization global success rate 24m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started Oct 30, 2025, 06:56 PM UTC· resolved Oct 30, 2025, 07:20 PM UTC

  1. investigating Oct 30, 2025, 06:56 PM 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 availability shortly. Mitigated: 10/30/2025 12:20:00 GMT-0700 (Pacific Daylight Time)

  2. resolved Oct 30, 2025, 07:20 PM UTC

    Resolved.

Read the full incident report →

Critical October 23, 2025 All US-West Requests Failing 25m US West 1, Console API

Started Oct 23, 2025, 12:10 AM UTC· resolved Oct 23, 2025, 12:35 AM UTC

  1. investigating Oct 23, 2025, 12:10 AM 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 should be fully recovered as of 5:35PM. Only configuration APIs for SDK initialization, background syncing, and console API was impacted. All other APIs are confirmed healthy during this incident. Mitigated: 10/22/2025 5:40 PM PST

  2. resolved Oct 23, 2025, 12:35 AM UTC

    Resolved.

Read the full incident report →

Major October 10, 2025 SDK Initialization SR Stability 9m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started Oct 10, 2025, 04:43 PM UTC· resolved Oct 10, 2025, 04:52 PM UTC

  1. investigating Oct 10, 2025, 04:43 PM 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 Daylight Time)

  2. resolved Oct 10, 2025, 04:52 PM UTC

    Resolved.

Read the full incident report →

Major October 9, 2025 Success Rate Drop for Europe North Region 5m Log Event API, Europe West 1

Started Oct 09, 2025, 03:30 PM UTC· resolved Oct 09, 2025, 03:35 PM UTC

  1. investigating Oct 09, 2025, 03:30 PM 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 Oct 09, 2025, 03:35 PM UTC

    Resolved.

Read the full incident report →

Major October 3, 2025 API Exports First Exposures Report Schema Breaking Change 1m Console API

Started Oct 03, 2025, 07:02 PM UTC· resolved Oct 03, 2025, 07:03 PM UTC

  1. investigating Oct 03, 2025, 07:02 PM 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 Oct 03, 2025, 07:03 PM UTC

    Resolved.

Read the full incident report →

Minor October 2, 2025 Some feature gates have a delay in Pulse results 16h 40m Experiment Results (Cloud)

Started Oct 02, 2025, 05:20 PM UTC· resolved Oct 03, 2025, 10:00 AM UTC

  1. investigating Oct 02, 2025, 05:20 PM 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 Oct 03, 2025, 10:00 AM UTC

    Resolved.

Read the full incident report →

Major September 19, 2025 Misconfiguration on consoleapi and event processing services 3d 10h Console API, Event Forwarding Pipeline (Warehouse Native)

Started Sep 19, 2025, 08:00 AM UTC· resolved Sep 22, 2025, 06:31 PM UTC

  1. investigating Sep 19, 2025, 08:00 AM 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 replayed. Mitigated: 09/22/2025 11:31:00 GMT-0700 (Pacific Daylight Time)

  2. resolved Sep 22, 2025, 06:31 PM UTC

    Resolved.

Read the full incident report →

Minor September 15, 2025 Propagation delay in server SDKs 1h 34m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started Sep 15, 2025, 05:03 PM UTC· resolved Sep 15, 2025, 06:37 PM UTC

  1. investigating Sep 15, 2025, 05:03 PM 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 Sep 15, 2025, 06:37 PM UTC

    Resolved.

Read the full incident report →

Major September 2, 2025 Elevated 5xx rate in EU Regions 50m Europe West 1

Started Sep 02, 2025, 06:44 PM UTC· resolved Sep 02, 2025, 07:34 PM UTC

  1. investigating Sep 02, 2025, 06:44 PM 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 Sep 02, 2025, 07:34 PM UTC

    Resolved.

Read the full incident report →

Critical August 25, 2025 Drop in success rate for /api/v1/log_event and /api/v1/rgstr 40m Log Event API

Started Aug 25, 2025, 06:20 PM UTC· resolved Aug 25, 2025, 07:00 PM UTC

  1. investigating Aug 25, 2025, 06:20 PM 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 Aug 25, 2025, 07:00 PM UTC

    Resolved.

Read the full incident report →

Critical August 15, 2025 Increase in Initialization Errors Client SDKs 39m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started Aug 15, 2025, 11:26 PM UTC· resolved Aug 16, 2025, 12:05 AM UTC

  1. investigating Aug 15, 2025, 11:26 PM 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 Aug 16, 2025, 12:05 AM UTC

    Resolved.

Read the full incident report →

Minor August 6, 2025 US East5 Latency Increase for Server SDK Initialization 3h 40m US East 5

Started Aug 06, 2025, 11:46 AM UTC· resolved Aug 06, 2025, 03:26 PM UTC

  1. investigating Aug 06, 2025, 11:46 AM 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 Aug 06, 2025, 03:26 PM UTC

    Resolved.

Read the full incident report →

Minor July 28, 2025 Rootcause Identified 1m US West 1

Started Jul 28, 2025, 08:48 PM UTC· resolved Jul 28, 2025, 08:49 PM UTC

  1. investigating Jul 28, 2025, 08:48 PM 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 Jul 28, 2025, 08:49 PM UTC

    Resolved.

Read the full incident report →

Minor July 28, 2025 Investigation Update 1m US West 1

Started Jul 28, 2025, 07:15 PM UTC· resolved Jul 28, 2025, 07:16 PM UTC

  1. investigating Jul 28, 2025, 07:15 PM 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 Jul 28, 2025, 07:16 PM UTC

    Resolved.

Read the full incident report →

Minor July 28, 2025 Elevated Latency in US-West 1h 5m US West 1, Log Event API

Started Jul 28, 2025, 02:45 PM UTC· resolved Jul 28, 2025, 03:50 PM UTC

  1. investigating Jul 28, 2025, 02:45 PM 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 Jul 28, 2025, 03:50 PM UTC

    Resolved.

Read the full incident report →

Major July 18, 2025 5xx Spike for Client SDK Initialization 11m US East 1

Started Jul 18, 2025, 03:10 PM UTC· resolved Jul 18, 2025, 03:21 PM UTC

  1. investigating Jul 18, 2025, 03:10 PM 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 be recovered. Update: 10:49AM PST, the rootcause was identified to be a GCP Outage: https://status.cloud.google.com/incidents/8cY8jdUpEGGbsSMSQk7J

  2. resolved Jul 18, 2025, 03:21 PM UTC

    Resolved.

Read the full incident report →

Major July 7, 2025 API Reliability Degraded in Europe North 25m Log Event API, Europe West 1

Started Jul 07, 2025, 08:05 PM UTC· resolved Jul 07, 2025, 08:30 PM UTC

  1. investigating Jul 07, 2025, 08:05 PM 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 Europe North have degraded significantly. We are addressing the issue to restore full reliability.

  2. resolved Jul 07, 2025, 08:30 PM UTC

    Resolved.

Read the full incident report →

Major July 4, 2025 Client SDK Initialization SR Dip in EU-West 3m Europe West 1

Started Jul 04, 2025, 07:25 PM UTC· resolved Jul 04, 2025, 07:28 PM UTC

  1. investigating Jul 04, 2025, 07:25 PM 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 Jul 04, 2025, 07:28 PM UTC

    Resolved.

Read the full incident report →

Major June 6, 2025 Elevated 5xx for Event Ingestion US East and EU West 17m Log Event API

Started Jun 06, 2025, 06:53 PM UTC· resolved Jun 06, 2025, 07:10 PM UTC

  1. investigating Jun 06, 2025, 06:53 PM 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 Investigating**: Elevated 5xx errors are occurring in the US East and EU West regions, with the recovery process underway.

  2. resolved Jun 06, 2025, 07:10 PM UTC

    Resolved.

Read the full incident report →

Minor June 5, 2025 Regional Issue for Client and Server SDKs 25m US East 1

Started Jun 05, 2025, 10:05 PM UTC· resolved Jun 05, 2025, 10:30 PM UTC

  1. investigating Jun 05, 2025, 10:05 PM 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 delays in receiving new configuration updates via Client and Server SDKs following modifications in the Statsig Console or through the Console API.

  2. resolved Jun 05, 2025, 10:30 PM UTC

    Resolved.

Read the full incident report →

Minor May 31, 2025 Streaming Data Delay 1h 10m Experiment Results (Cloud), Event Forwarding Pipeline (Warehouse Native)

Started May 31, 2025, 01:20 AM UTC· resolved May 31, 2025, 02:30 AM UTC

  1. investigating May 31, 2025, 01:20 AM 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 impacting streaming pipelines, affecting real-time features such as Metrics Explorer.

  2. resolved May 31, 2025, 02:30 AM UTC

    Resolved.

Read the full incident report →

Major May 6, 2025 Initialized endpoints have elevated error rates for 3 regions 17m US West 1, US East 1, US East 5, Europe West 1 and 1 more

Started May 06, 2025, 05:45 PM UTC· resolved May 06, 2025, 06:02 PM UTC

  1. investigating May 06, 2025, 05:45 PM 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 isolated to a single customer. Mitigated: 05/06/2025 11:02:00 GMT-0700 (Pacific Daylight Time)

  2. resolved May 06, 2025, 06:02 PM UTC

    Resolved.

Read the full incident report →