Vendor Status Watch

← all vendors

BigLeaf status history

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

1incidents, last 30 days
3incidents, last 90 days
12incidents on record
Incidents per week, last 12 weeks:

How long do BigLeaf incidents last?

2.1 hmedian incident duration12 measured
3.6 h90th percentile1 in 10 ran longer
2.4 hmedian, major/critical only2 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-11 13:34 UTCBigleaf Cloud Connect Dashboard DOWNresolvedcritical2 h 56 min
2026-07-08 16:55 UTCBigleaf Cloud Connect Dashboard and API functionalityresolvedminor1 h 16 min
2026-06-18 14:39 UTCNetwork Performance Issues - NYCresolvedminor4 h 07 min
2026-04-30 17:53 UTCNetwork Performance Issues - ATLresolvednone2 h 06 min
2026-02-20 19:00 UTCNetwork Performance Issues - LAXresolvedminor2 h 29 min
2025-12-04 19:31 UTCNetwork Performance Issues - LAXresolvednone3 h 36 min
2025-10-02 19:54 UTCBigleaf Cloud Connect Dashboard Slow or Unresponsiveresolvedminor2 h 03 min
2025-09-26 17:01 UTCEmergency Maintenance - Seattle PoPresolvednone3 h 28 min
2025-09-18 16:19 UTCBigleaf Cloud Connect Dashboard Slow or Unresponsiveresolvednone1 h 08 min
2025-09-12 12:41 UTCMissing Site Metricsresolvedmajor1 h 48 min
2025-09-11 20:07 UTCEmergency Maintenance - Frankfurt, DE Gateway Clusterresolvedminor1 h 33 min
2025-08-22 17:31 UTCBigleaf Cloud Connect Dashboard DOWNresolvedminor1 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
}