Teamwork status history
Current state: operational — “All Systems Operational” per https://status.teamwork.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Teamwork incidents last?
From 26 incidents with a vendor-posted start and resolve time. Longest on record: Service Disruption: Slack Integration Unavailable — 3.3 days (2026-02-28 08: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 (26)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-22 15:48 UTC | Slow loading issue | resolved | minor | 2 h 44 min |
| 2026-05-28 08:40 UTC | We are investigating issues with Teamwork application performance in the EU region | resolved | minor | 6 h 40 min |
| 2026-05-01 08:04 UTC | Teamwork Desk - delay in data appearing in search results and reports | resolved | minor | 6 h 03 min |
| 2026-04-20 15:49 UTC | Teamwork Projects - Service Degradation in the US region | resolved | minor | 4 h 33 min |
| 2026-03-24 20:41 UTC | Investigating issues creating and cloning projects in the EU Region | resolved | minor | 50 min |
| 2026-03-16 14:06 UTC | Chat Issue in US region | resolved | critical | 3 h 26 min |
| 2026-03-12 08:55 UTC | Intermittent issues with Projects Application | resolved | none | 37 min |
| 2026-03-11 17:29 UTC | Investing reports of loading Issues | resolved | major | 1 h 54 min |
| 2026-03-04 17:19 UTC | Projects load issues | resolved | minor | 50 min |
| 2026-02-28 08:47 UTC | Service Disruption: Slack Integration Unavailable | resolved | minor | 3 d 6 h |
| 2026-02-25 10:19 UTC | Investigating: Email Delivery Delays to Microsoft Email Addresses | resolved | minor | 28 h 09 min |
| 2026-02-16 15:14 UTC | Investigating delayed processing of emails in Teamwork Desk | resolved | minor | 39 min |
| 2026-02-10 21:31 UTC | Service Outage in EU Region | resolved | critical | 1 h 11 min |
| 2026-01-14 22:32 UTC | Teamwork Projects - Service Degradation. | resolved | minor | 36 min |
| 2026-01-12 16:51 UTC | Teamwork Slow Loading Issue | resolved | minor | 3 h 08 min |
| 2025-12-10 13:43 UTC | Projects loading issues | resolved | minor | 3 h 06 min |
| 2025-12-08 16:32 UTC | Load issues with Teamwork | resolved | minor | 2 h 38 min |
| 2025-12-01 16:45 UTC | Teamwork Slow Loading | resolved | major | 3 h 59 min |
| 2025-11-13 16:39 UTC | Teamwork Desk - Mail delivery - Degraded Performance | resolved | minor | 1 h 31 min |
| 2025-11-05 12:19 UTC | Service Outage in US Region | resolved | major | 58 min |
| 2025-10-29 13:43 UTC | Teamwork Loading | resolved | minor | 3 h 20 min |
| 2025-10-27 09:00 UTC | Teamwork Desk: issue with tickets | resolved | minor | 4 h 01 min |
| 2025-10-17 10:12 UTC | Teamwork Desk: Sending Replies | resolved | minor | 24 min |
| 2025-10-13 14:23 UTC | Teamwork Loading Issue (US Region) | resolved | critical | 1 h 57 min |
| 2025-09-30 14:08 UTC | Investigation Loading Issues with Teamwork Desk and Chat (US Region) | resolved | none | 3 h 24 min |
| 2025-08-14 16:40 UTC | Unexpected Teamwork Desk & Chat disruption in the US region | resolved | major | 1 h 01 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 Teamwork with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"teamwork"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}