BigLeaf status history
Current state: operational — “All Systems Operational” per https://status.bigleaf.net (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do BigLeaf incidents last?
From 12 incidents with a vendor-posted start and resolve time. Longest on record: Network Performance Issues - NYC — 4.1 h (2026-06-18 14:39 UTC). Excluded, never estimated: nothing. 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 (12)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-11 13:34 UTC | Bigleaf Cloud Connect Dashboard DOWN | resolved | critical | 2 h 56 min |
| 2026-07-08 16:55 UTC | Bigleaf Cloud Connect Dashboard and API functionality | resolved | minor | 1 h 16 min |
| 2026-06-18 14:39 UTC | Network Performance Issues - NYC | resolved | minor | 4 h 07 min |
| 2026-04-30 17:53 UTC | Network Performance Issues - ATL | resolved | none | 2 h 06 min |
| 2026-02-20 19:00 UTC | Network Performance Issues - LAX | resolved | minor | 2 h 29 min |
| 2025-12-04 19:31 UTC | Network Performance Issues - LAX | resolved | none | 3 h 36 min |
| 2025-10-02 19:54 UTC | Bigleaf Cloud Connect Dashboard Slow or Unresponsive | resolved | minor | 2 h 03 min |
| 2025-09-26 17:01 UTC | Emergency Maintenance - Seattle PoP | resolved | none | 3 h 28 min |
| 2025-09-18 16:19 UTC | Bigleaf Cloud Connect Dashboard Slow or Unresponsive | resolved | none | 1 h 08 min |
| 2025-09-12 12:41 UTC | Missing Site Metrics | resolved | major | 1 h 48 min |
| 2025-09-11 20:07 UTC | Emergency Maintenance - Frankfurt, DE Gateway Cluster | resolved | minor | 1 h 33 min |
| 2025-08-22 17:31 UTC | Bigleaf Cloud Connect Dashboard DOWN | resolved | minor | 1 h 08 min |
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 BigLeaf with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"bigleaf"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}