https://approjects-vendor-status-watch.static.hf.space/v/sapling.htmlIncidents from Sapling's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/qnlwjkp5c79wsapling:2026-09-11T00:39:47.902ZFri, 11 Sep 2026 00:39:47 +0000From 4:30 to 5:30pm PDT on Sep. 10, 2026, a database migration overloaded the production database with two other read-heavy jobs running at the same time. The issue has been identified and resolved.https://stspg.io/7pvc1w7q9xt5sapling:2026-07-12T19:15:19.085ZSun, 12 Jul 2026 19:15:19 +0000This incident has been resolved.https://stspg.io/vjk444r00ygcsapling:2026-07-06T17:18:52.587ZMon, 06 Jul 2026 17:18:52 +0000This incident has been resolved.https://stspg.io/l92pcwmlxntrsapling:2026-06-15T01:47:38.000ZMon, 15 Jun 2026 01:47:38 +0000This incident has been resolved.https://stspg.io/6cfscv658ch8sapling:2026-01-25T12:30:00.000ZSun, 25 Jan 2026 12:30:00 +0000From 4:40am to 7:40am PST on Jan 25, 2026, the cluster experienced downtime due to expired trust anchors. New certs have been generated.https://stspg.io/gzqlvjbjxwnpsapling:2026-01-16T23:24:06.647ZFri, 16 Jan 2026 23:24:06 +0000This has been resolved for over 6 days with the new integration. We left the message so those with the older integration would update.https://stspg.io/5jl8ymc0y9wmsapling:2025-12-30T23:00:00.000ZTue, 30 Dec 2025 23:00:00 +0000This incident has been resolved.https://stspg.io/qvy88zdj2chwsapling:2025-11-26T11:00:00.000ZWed, 26 Nov 2025 11:00:00 +0000AWS cluster upgrades led to insufficient AI detection pod assignment, leading to latency and then downtime starting from 10:30am PST.https://stspg.io/sfrrgdchw6c2sapling:2025-11-11T10:00:00.000ZTue, 11 Nov 2025 10:00:00 +0000AWS 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 pohttps://stspg.io/7r38v6t1s26ysapling:2025-11-07T23:24:48.432ZFri, 07 Nov 2025 23:24:48 +0000This incident has been resolved.https://stspg.io/4cm379ptv7h8sapling:2025-10-08T18:33:02.277ZWed, 08 Oct 2025 18:33:02 +0000This incident has been resolved.https://stspg.io/1y6qlzh439d1sapling:2025-10-07T17:15:23.464ZTue, 07 Oct 2025 17:15:23 +0000Subset of pods failing to connect to caching system after caching system upgrade led to degraded serviceshttps://stspg.io/630zfd0drp9tsapling:2025-09-27T15:45:54.000ZSat, 27 Sep 2025 15:45:54 +0000Delays when writing to S3 resulted in latency spikes across endpoints.