Stacker status history

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

0incidents, last 30 days

2incidents, last 90 days

5incidents on record

Incidents per week, last 12 weeks:

Get Stacker alerts in your Slack — free template RSS for Stacker

How long do Stacker incidents last?

21 minmedian incident duration4 measured

3.3 h90th percentile1 in 10 ran longer

21 minmedian, major/critical only4 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Unable to access Stacker apps — 3.3 h (2026-02-20 19:58 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 (5)

Started	Incident	Status	Impact	Duration
2026-07-10 16:23 UTC	Astra outage from failed deployment	resolved	critical	9 min
2026-06-26 14:42 UTC	Unscheduled database manitenance	resolved	major	34 min
2026-03-20 12:15 UTC	Unscheduled database restart	resolved	maintenance	28 min
2026-02-20 19:58 UTC	Unable to access Stacker apps	resolved	critical	3 h 20 min
2026-02-03 14:29 UTC	Stacker Access Down	resolved	critical	5 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 Stacker with the template

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

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