Sapling Intelligence Status Page

Jan 16, 2026 · resolved Jan 25

This has been resolved for over 6 days with the new integration. We left the message so those with the older integration would update.

Jan 25, 2026 · resolved Jan 25

From 4:40am to 7:40am PST on Jan 25, 2026, the cluster experienced downtime due to expired trust anchors. New certs have been generated.

Dec 30, 2025 · resolved Dec 30

This incident has been resolved.

Nov 26, 2025 · resolved Nov 26

AWS cluster upgrades led to insufficient AI detection pod assignment, leading to latency and then downtime starting from 10:30am PST.

Nov 11, 2025 · resolved Nov 11

AWS announced end of support for AMIs that Sapling used in its EKS cluster. ``` Amazon EKS will end support for EKS optimized AL2 AMIs on November 26, 2025. To avoid any disruptions, please migrate your workloads to alternative AMI types before November 26, 2025. ``` Around midnight Pacific Time on November 10, 2025, Sapling’s Helm configuration was updated with the updated AMIs. No disruption was observed. However, around 2am Pacific Time on November 11, 2025, the main backend K8S pods on Sapling were unable to be assigned to new nodes due to node affinity settings. This resulted in requests timing out and failing, affecting API, extension, and website users. Around 7:30am Pacific Time, the AMI update was fixed and the instances were updated. With the redeployment of the existing pods as well as the Linkerd mesh, most services were restored around 7:45am Pacific Time, with the remaining services up and running around 8:05am PT. Future updates of the AMI will be performed shortly before midnight Friday time, with monitoring to see if pods are assigned to new instances without any node affinity issues.