Changes / Statsig / Client SDK Initialization and Event Logging Unavailable for 5 minutes
Statsig: Critical incident: Client SDK Initialization and Event Logging Unavailable for 5 minutes
Summary
Statsig reported a critical outage from 2025-11-07 00:33 UTC to 2025-11-07 00:38 UTC, lasting 5 min. Client SDK initialization failed for a majority of requests, and event logging calls also failed. The incident was resolved; Statsig expected most events to be recoverable through SDK-level retries.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Client SDK Initialization and Event Logging Unavailable for 5 minutes
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2025-11-07 00:33 UTC
Before: not present
After: 2025-11-07 00:38 UTC
Before: not present
After: Asia Southeast 1, Config Delivery API - Asia Southeast 1, Config Delivery API - Europe West 1, Config Delivery API - US East 1, Config Delivery API - US East 5, Config Delivery API - US West 1, Europe West 1, Log Event API, US East 1, US East 5, US West 1
Before: not present
After: 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)
Before: not present
After: Resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Client SDK Initialization and Event Logging Unavailable for 5 minutes (this change) Statsig reported a critical outage from 2025-11-07 00:33 UTC to 2025-11-07 00:38 UTC, lasting 5 min. Client SDK initialization failed for a majority of requests, and event logging calls also failed. The incident was resolved; Statsig expected most events to be recoverable through SDK-level retries. | Major incident |