Sapling incident

Increased multilingual usage leading to some timeouts

Major Resolved View vendor source →

Sapling experienced a major incident on April 30, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2025, 02:32 AM UTC
Resolved
Apr 30, 2025, 02:32 AM UTC
Duration
—
Detected by Pingoru
Apr 30, 2025, 02:32 AM UTC

Update timeline

  1. resolved Apr 30, 2025, 02:32 AM UTC

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

  2. postmortem Apr 30, 2025, 05:38 AM UTC

    Increased load to multilingual handling as well as increased latency when sending Amplitude events led to degraded latency for other endpoints.