Jan <var data-var='date'>25</var>, <var data-var='time'>15:46</var> UTC Resolved - 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 <var data-var='date'>19</var>, <var data-var='time'>07:20</var> UTC Update - We are continuing to monitor for any further issues.Jan <var data-var='date'>17</var>, <var data-var='time'>06:53</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'>16</var>, <var data-var='time'>23:38</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>16</var>, <var data-var='time'>23:24</var> UTC Investigating - We are currently patching this issue -- the extension will not work in Chrome v144

Chrome 144 breaking change for runtime.onMessage

Jan <var data-var='date'>25</var>, <var data-var='time'>12:30</var> UTC Resolved - 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.

linkerd expired anchors led to cluster downtime

Dec <var data-var='date'>30</var>, <var data-var='time'>23:00</var> UTC Resolved - This incident has been resolved.

/edits and /spellcheck APIs team_id argument error

Nov <var data-var='date'>26</var>, <var data-var='time'>11:00</var> UTC Resolved - AWS cluster upgrades led to insufficient AI detection pod assignment, leading to latency and then downtime starting from 10:30am PST.

AI detect downtime

Nov <var data-var='date'>11</var>, <var data-var='time'>10:00</var> UTC Resolved - AWS no longer supported older AMI, hence forcing upgrade. However, this resulted in certain nodegroups changing and pods not beeing assigned.

Downtime due to new AWS AMI upgrade

Nov <var data-var='date'> 8</var>, <var data-var='time'>04:01</var> UTC Resolved - This incident has been resolved.Nov <var data-var='date'> 7</var>, <var data-var='time'>23:24</var> UTC Monitoring - Limited resources in AWS region have led to insufficient AI detector pods since 11/5

AI detector pods overloaded

Oct <var data-var='date'> 8</var>, <var data-var='time'>18:47</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 8</var>, <var data-var='time'>18:33</var> UTC Monitoring - We have seen a surge in spellcheck usage in the past day resulting in some scaling of the cluster components needed.

Spellcheck latency

Oct <var data-var='date'> 7</var>, <var data-var='time'>17:15</var> UTC Resolved - Subset of pods failing to connect to caching system after caching system upgrade led to degraded services

Spellcheck API / service request failures

Sep <var data-var='date'>27</var>, <var data-var='time'>15:45</var> UTC Resolved - Delays when writing to S3 resulted in latency spikes across endpoints.

High latency

Apr <var data-var='date'>30</var>, <var data-var='time'>02:32</var> UTC Resolved - A fix has been implemented and we are monitoring the results.

Increased multilingual usage leading to some timeouts

Apr <var data-var='date'>16</var>, <var data-var='time'>05:30</var> UTC Resolved - A shortage of available pods resulted in latency spike starting around 10:20 PDT

Latency spike

Feb <var data-var='date'>20</var>, <var data-var='time'>15:00</var> UTC Resolved - Increase in latency due to upgrades to libraries for error classification pipeline.

Increased latency

Nov <var data-var='date'>20</var>, <var data-var='time'>20:36</var> UTC Resolved - This incident has been resolved.Nov <var data-var='date'>20</var>, <var data-var='time'>20:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.

Cluster capacity reached

Oct <var data-var='date'>18</var>, <var data-var='time'>22:30</var> UTC Resolved - Due to Linkerd issues, services outside of /edits (primarily autocomplete and AI detection) were degraded / unavailable.

Non-edits services unavailable / degraded perforamnce

Oct <var data-var='date'> 8</var>, <var data-var='time'>16:10</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 8</var>, <var data-var='time'>15:52</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Oct <var data-var='date'> 8</var>, <var data-var='time'>15:43</var> UTC Identified - The issue has been identified and a fix is being implemented.

Memory utilization spike

Jun <var data-var='date'>18</var>, <var data-var='time'>21:55</var> UTC Resolved - This incident has been resolved.Jun <var data-var='date'>18</var>, <var data-var='time'>21:15</var> UTC Investigating - We have identified the issue and are resolving

Rephrase service down

Mar <var data-var='date'>21</var>, <var data-var='time'>07:00</var> UTC Resolved - SDK would display error from 3/20 5pm to 3/21 11am Pacific Time for empty edits array due to a backend inconsistency.

Edits API and SDK incompatibility

Jan <var data-var='date'>13</var>, <var data-var='time'>14:30</var> UTC Resolved - From 6:30 to 9AM PT, there was degraded performance due to issues with server database and caching system.

Degraded performance

Oct <var data-var='date'>20</var>, <var data-var='time'>02:06</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'>20</var>, <var data-var='time'>00:25</var> UTC Update - Issue has been resolved.Oct <var data-var='date'>19</var>, <var data-var='time'>19:38</var> UTC Investigating - We are currently investigating the issue.

Cluster update resulting in downtime

Sep <var data-var='date'>28</var>, <var data-var='time'>20:30</var> UTC Resolved - Due to some configuration issues when scaling our servers, users may have experienced degraded API performance.

Degraded API performance

Jul <var data-var='date'>26</var>, <var data-var='time'>00:04</var> UTC Resolved - This incident has been resolved.Jul <var data-var='date'>25</var>, <var data-var='time'>23:09</var> UTC Investigating - We are currently investigating this issue.

Load balancer issues

Jul <var data-var='date'>19</var>, <var data-var='time'>19:00</var> UTC Resolved - From around 11:30pm to 1:30pm PT most suggested edits were filtered. This has been resolved.

Filtered edits

Jun <var data-var='date'>28</var>, <var data-var='time'>05:30</var> UTC Resolved - Higher latency than usual from 6/27/2023 10:30pm PT to 2/28/2023 8:30am PT.

Degraded edits performance

Jan <var data-var='date'>24</var>, <var data-var='time'>04:30</var> UTC Resolved - Downtime on 1/23 from 8:45pm to 9:45pm PT

Downtime

Jan <var data-var='date'> 6</var>, <var data-var='time'>04:30</var> UTC Resolved - Degraded edits performance with timeouts from 1/5/2023 9pm PT to 1/6/2023 9am PT

Is Sapling Intelligence down?

Sapling Intelligence status is UP

Lastest published events

Chrome 144 breaking change for runtime.onMessage

linkerd expired anchors led to cluster downtime

/edits and /spellcheck APIs team_id argument error

Sapling Intelligence Services, Components and Regions

Recent Sapling Intelligence events

Chrome 144 breaking change for runtime.onMessage

linkerd expired anchors led to cluster downtime

/edits and /spellcheck APIs team_id argument error

AI detect downtime

Downtime due to new AWS AMI upgrade

AI detector pods overloaded

Get your FREE account now,
5 monitors included!

Is Sapling Intelligence down?

Sapling Intelligence status is UP

Lastest published events

Chrome 144 breaking change for runtime.onMessage

linkerd expired anchors led to cluster downtime

/edits and /spellcheck APIs team_id argument error

Sapling Intelligence Services, Components and Regions

Recent Sapling Intelligence events

Chrome 144 breaking change for runtime.onMessage

linkerd expired anchors led to cluster downtime

/edits and /spellcheck APIs team_id argument error

AI detect downtime

Downtime due to new AWS AMI upgrade

AI detector pods overloaded

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!