Vendor Status Watch

← all vendors

SashiDo status history

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

0incidents, last 30 days
0incidents, last 90 days
20incidents on record

How long do SashiDo incidents last?

99 minmedian incident duration20 measured
2.9 h90th percentile1 in 10 ran longer
median, major/critical onlynone posted

From 20 incidents with a vendor-posted start and resolve time. Longest on record: [EU/APPS] - Elevated applications errors — 10.3 days (2026-03-22 08:17 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 (20)

StartedIncidentStatusImpactDuration
2026-05-22 09:11 UTC[EU/APPS] - Elevated applications errorsresolvedminor2 h 14 min
2026-05-12 13:18 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 40 min
2026-04-23 16:47 UTC[NA/APPS] - Increased rate of applications health errorsresolvedminor1 h 31 min
2026-04-13 17:48 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 34 min
2026-03-25 12:54 UTC[Builds and Deployments] - Dashboard Synchronization Issuesresolvednone4 d 22 h
2026-03-22 08:17 UTC[EU/APPS] - Elevated applications errorsresolvednone10 d 6 h
2026-03-02 16:16 UTC[NA/APPS] - Elevated applications errorsresolvedminor1 h 34 min
2026-02-10 21:31 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 32 min
2026-01-20 12:48 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 45 min
2025-12-29 00:02 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 39 min
2025-12-19 18:16 UTC[NA/APPS] - Elevated applications errorsresolvedminor1 h 33 min
2025-12-02 14:12 UTC[NA/APPS] - Increased rate of applications health errorsresolvednone1 h 44 min
2025-11-13 14:28 UTC[NA/APPS] - Elevated applications errorsresolvedminor1 h 36 min
2025-11-05 20:16 UTC[NA/APPS] - Elevated applications errorsresolvedminor1 h 31 min
2025-10-28 08:58 UTC[NA/APPS] - Increased rate of applications health errorsresolvedminor2 h 07 min
2025-10-26 01:39 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor2 h 49 min
2025-10-02 23:18 UTC[NA/APPS] - Increased rate of unhealthy applicationsresolvedminor1 h 34 min
2025-09-16 14:36 UTC[NA/APPS] - Increased rate of applications health errorsresolvedminor2 h 52 min
2025-09-08 23:22 UTC[NA/APPS] - Elevated applications errorsresolvedminor1 h 36 min
2025-08-19 12:59 UTC[NA/APPS] - Increased rate of applications health errorsresolvednone1 h 56 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 SashiDo with the template

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

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