Vendor Status Watch

← all vendors

Teamwork status history

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

1incidents, last 30 days
1incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:

How long do Teamwork incidents last?

2.7 hmedian incident duration26 measured
6.0 h90th percentile1 in 10 ran longer
115 minmedian, major/critical only6 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-24 10:42 UTCIssue with tasks creation in Projectsresolvednone39 min
2026-06-22 15:48 UTCSlow loading issueresolvedminor2 h 44 min
2026-05-28 08:40 UTCWe are investigating issues with Teamwork application performance in the EU regionresolvedminor6 h 40 min
2026-05-01 08:04 UTCTeamwork Desk - delay in data appearing in search results and reportsresolvedminor6 h 03 min
2026-04-20 15:49 UTCTeamwork Projects - Service Degradation in the US regionresolvedminor4 h 33 min
2026-03-24 20:41 UTCInvestigating issues creating and cloning projects in the EU Regionresolvedminor50 min
2026-03-16 14:06 UTCChat Issue in US regionresolvedcritical3 h 26 min
2026-03-12 08:55 UTCIntermittent issues with Projects Applicationresolvednone37 min
2026-03-11 17:29 UTCInvesting reports of loading Issuesresolvedmajor1 h 54 min
2026-03-04 17:19 UTCProjects load issuesresolvedminor50 min
2026-02-28 08:47 UTCService Disruption: Slack Integration Unavailableresolvedminor3 d 6 h
2026-02-25 10:19 UTCInvestigating: Email Delivery Delays to Microsoft Email Addressesresolvedminor28 h 09 min
2026-02-16 15:14 UTCInvestigating delayed processing of emails in Teamwork Deskresolvedminor39 min
2026-02-10 21:31 UTCService Outage in EU Regionresolvedcritical1 h 11 min
2026-01-14 22:32 UTCTeamwork Projects - Service Degradation.resolvedminor36 min
2026-01-12 16:51 UTCTeamwork Slow Loading Issueresolvedminor3 h 08 min
2025-12-10 13:43 UTCProjects loading issuesresolvedminor3 h 06 min
2025-12-08 16:32 UTCLoad issues with Teamworkresolvedminor2 h 38 min
2025-12-01 16:45 UTCTeamwork Slow Loadingresolvedmajor3 h 59 min
2025-11-13 16:39 UTCTeamwork Desk - Mail delivery - Degraded Performanceresolvedminor1 h 31 min
2025-11-05 12:19 UTCService Outage in US Regionresolvedmajor58 min
2025-10-29 13:43 UTCTeamwork Loadingresolvedminor3 h 20 min
2025-10-27 09:00 UTCTeamwork Desk: issue with ticketsresolvedminor4 h 01 min
2025-10-17 10:12 UTCTeamwork Desk: Sending Repliesresolvedminor24 min
2025-10-13 14:23 UTCTeamwork Loading Issue (US Region)resolvedcritical1 h 57 min
2025-09-30 14:08 UTCInvestigation Loading Issues with Teamwork Desk and Chat (US Region)resolvednone3 h 24 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
}