Statsig incident

Statsig experiencing propagation delays

Resolved after 1 hour 50 minutes, affecting US West 1 and US East 1 and 1 more, on March 30, 2026.

investigating Jun 09, 2026, 06:16 AM 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)

Started
Mar 30, 2026, 08:20 PM UTC
Resolved
Mar 30, 2026, 10:10 PM UTC
Duration
1h 50m
Detected by Pingoru
Mar 30, 2026, 08:20 PM UTC

Affected components

US West 1US East 1US East 5Europe West 1Asia Southeast 1

Update timeline

  1. investigating Jun 09, 2026, 06:16 AM 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)

  2. resolved Jun 09, 2026, 06:16 AM UTC

    Resolved.

Your product runs on more than Statsig

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →