Vendor Status Watch

← all vendors

GoodTime status history

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

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

How long do GoodTime incidents last?

5.3 hmedian incident duration6 measured
14.9 h90th percentile1 in 10 ran longer
—median, major/critical onlynone posted

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Out of date search results — 23.0 h (2025-11-04 14:12 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 (6)

StartedIncidentStatusImpactDuration
2026-07-30 12:44 UTCAgentic Services are downresolvednone4 h 20 min
2026-04-17 16:59 UTCPartial Lever Outagesresolvednone6 h 13 min
2025-11-04 14:12 UTCOut of date search resultsresolvedminor23 h 01 min
2025-10-24 14:44 UTCSlow response timeresolvednone1 h 08 min
2025-10-20 08:52 UTCAWS and other third party services outageresolvednone14 h 54 min
2025-10-09 16:25 UTCSearch not respondingresolvednone11 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 GoodTime with the template

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

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