Changes / Statsig / Initialized endpoints have elevated error rates for 3 regions
Statsig: Major incident: Initialized endpoints have elevated error rates for 3 regions
Summary
Statsig reported a major incident with elevated initialization endpoint errors affecting client SDK initialization; impact was isolated to a single customer. It started at 2025-05-06 17:45 UTC and was resolved at 2025-05-06 18:02 UTC, lasting 17 min. The team reverted the change that caused the errors and gated off the rollout.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Initialized endpoints have elevated error rates for 3 regions
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-05-06 17:45 UTC
Before: not present
After: 2025-05-06 18:02 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, US East 1, US East 5, US West 1
Before: not present
After: 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)
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 |
|---|---|---|
| Major incident: Initialized endpoints have elevated error rates for 3 regions (this change) Statsig reported a major incident with elevated initialization endpoint errors affecting client SDK initialization; impact was isolated to a single customer. It started at 2025-05-06 17:45 UTC and was resolved at 2025-05-06 18:02 UTC, lasting 17 min. The team reverted the change that caused the errors and gated off the rollout. | Major incident |