TeamSupport status history
Current state: operational — “All Systems Operational” per http://status.teamsupport.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do TeamSupport incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Performance slowness Identified! — 5.8 h (2026-03-30 16:47 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 (5)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-01 16:04 UTC | Messaging & Live Chat platform Outage | resolved | minor | 3 h 21 min |
| 2026-08-07 19:21 UTC | Messaging & Live Chat platform Outage | resolved | critical | 39 min |
| 2026-03-30 16:47 UTC | Performance slowness Identified! | resolved | minor | 5 h 48 min |
| 2025-11-03 14:53 UTC | Performance slowness Identified! | resolved | minor | 14 min |
| 2025-10-20 09:52 UTC | One of our Service Providers experienced an outage starting at 2:30 AM CST. The outage appears to be resolving itself | resolved | major | 3 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 TeamSupport with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"teamsupport"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
