Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Teamwork Outage History

Every past Teamwork outage tracked by IsDown, with detection times, duration, and resolution details.

There were 293 Teamwork outages since August 2019. The 35 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 24, 2026

March 2026: Investigating issues creating and cloning projects in the EU Region

Detected Mar 24, 2026 4:41 PM EDT · Resolved Mar 24, 2026 5:32 PM EDT · Duration about 1 hour

Teamwork experienced issues with creating and cloning projects in the EU Region for 51 minutes. The incident affected Teamwork Projects functionality specifically for EU Region users. The service team investigated and resolved the issue.

Major March 16, 2026

March 2026: Chat Issue in US region

Detected Mar 16, 2026 10:06 AM EDT · Resolved Mar 16, 2026 1:34 PM EDT · Duration about 3 hours

Teamwork Chat experienced a major service disruption in the US region that lasted 3.5 hours. The incident affected users' ability to access or use the chat functionality within the US region. The issue was identified and resolved with a implemented fix, followed by monitoring to ensure stability.

Minor March 12, 2026

March 2026: Intermittent issues with Projects Application

Detected Mar 12, 2026 4:55 AM EDT · Resolved Mar 12, 2026 5:36 AM EDT · Duration 41 minutes

Teamwork Projects experienced intermittent issues in the EU Region for 41 minutes. The service team identified the root cause and implemented a fix. The incident was fully resolved after a brief monitoring period.

Minor March 12, 2026

March 2026: Projects issue

Detected Mar 12, 2026 4:55 AM EDT · Resolved Mar 12, 2026 5:04 AM EDT · Duration 9 minutes

Teamwork experienced a minor issue affecting Projects in the EU Region for 9 minutes on March 12, 2026. The incident was under investigation as of 08:55 UTC. No resolution details were provided in the available updates.

Major March 11, 2026

March 2026: Investing reports of loading Issues

Detected Mar 11, 2026 1:29 PM EDT · Resolved Mar 11, 2026 3:28 PM EDT · Duration about 2 hours

Teamwork Projects in the US region experienced loading issues that prevented users from navigating between projects, with clicks on project links being unresponsive. The incident lasted 2 hours before a fix was implemented and the service was restored to normal operation.

Minor March 4, 2026

March 2026: Projects load issues

Detected Mar 4, 2026 12:19 PM EST · Resolved Mar 4, 2026 1:12 PM EST · Duration about 1 hour

Teamwork Projects experienced loading issues in the US region for 53 minutes. The service disruption prevented users from properly accessing their projects during this period. The issue was identified and resolved with a implemented fix, followed by monitoring to ensure stability.

Minor February 28, 2026

February 2026: Service Disruption: Slack Integration Unavailable

Detected Feb 28, 2026 3:47 AM EST · Resolved Mar 3, 2026 10:02 AM EST · Duration 3 days

The Teamwork.com Slack integration became unavailable, preventing users from sending notifications to Slack and using Slack-based functionality across both US and EU regions. The disruption lasted 78.3 hours and affected Teamwork Projects in both regions. The issue was resolved by working with Slack partners to restore the integration on the Slack Marketplace, requiring users to re-authenticate their Slack accounts to resume connectivity.

Minor February 25, 2026

February 2026: Investigating: Email Delivery Delays to Microsoft Email Addresses

Detected Feb 25, 2026 5:19 AM EST · Resolved Feb 26, 2026 9:32 AM EST · Duration 1 day

Teamwork experienced email delivery delays and failures for notifications sent to free Microsoft email addresses (@live, @hotmail, @outlook) across both US and EU regions for Teamwork Desk and Projects services. The issue affected only Microsoft domains while emails to other providers and custom domains continued working normally. The incident was resolved after 28.2 hours of investigation and collaboration with the email delivery provider.