Vendor Status Watch

← all vendors

Zenduty status history

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

1incidents, last 30 days
2incidents, last 90 days
4incidents on record
Incidents per week, last 12 weeks:
Get Zenduty alerts in your Slack — free templateRSS for Zenduty

How long do Zenduty incidents last?

20 minmedian incident duration4 measured
5.1 days90th percentile1 in 10 ran longer
—median, major/critical onlynone posted

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Voice call notification delivery failures - Singapore — 5.1 days (2026-07-17 11:48 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 (4)

StartedIncidentStatusImpactDuration
2026-09-01 12:52 UTCDelayed Incident Notificationsresolvedminor0 min
2026-07-17 11:48 UTCVoice call notification delivery failures - Singaporeresolvedminor5 d 2 h
2026-06-02 12:37 UTCWe had a partial degradation in notification servicepostmortemminor0 min
2025-10-20 09:31 UTCInvestigating Potential Issue - Delayed Notifications(SMS/Voice/Email) and impact to Email Integrationresolvedminor40 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 Zenduty with the template

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

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