← all vendors

Sapling status history

Current state: operational — “All Systems Operational” per https://sapling.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

How long do Sapling incidents last?

From 12 incidents with a vendor-posted start and resolve time. Longest on record: Chrome 144 breaking change for runtime.onMessage — 8.7 days (2026-01-16 23:24 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (13)

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Sapling with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "sapling"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}