New Multi-region uptime checks and custom-domain status pages

Sapling Intelligence Outage History

Daily provider-status observations and published incident history for Sapling Intelligence.

Operational

Sapling Intelligence is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Sapling Intelligence for future changes.

100% of 37 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

3 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
DNS server update downtime
Source not attested
Last archived state: resolved
View archived record details
monitoring
Planned downtime to system starting around 11am PDT on July 12, 2026.
Website unexpected instance reboot
major Source not attested
Last archived state: resolved
View archived record details
identified
Website server needed unexpected reboot
June 2026
/edits model downtime
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Upgrade of model resulted in unexpected downtime due to mis-specified model ID