Is TeamDynamix down?

An upstream network issue is causing delays in connectivity to external systems for the Work Management platform.

As of 1:07AM ET traffic is flowing normally and backend services are processing the backlog.

This issue was confirmed resolved as of 1:07AM ET on 6/10/2026. The upstream network issue has been resolved, and additional monitoring has been put in place to better capture the issue in the future.

We are investigating an issue regarding the usage of the Web API to create tickets which results in specified custom attributes not having values set for them.

We are in the process of rolling out a hotfix for this issue, which we will monitor to confirm it has fully addressed the issue.

At this time the rollout of the hotfix for the ticket creation API issue has completed. The fix has successfully addressed the issues reported regarding custom attributes on tickets being populated. This incident will be considered resolved.

We are experiencing a backend service outage. We are working to identify the root cause and resolve as soon as possible.

The issue began at 3:45pm ET and a fix was deployed at 4:04pm ET. We are monitoring the effectiveness of the fix.

All affected backend services are fully operational. A full post-mortem will be posted to the incident.

On May 21, 2026 from 3:45PM ET to 4:04PM ET \(19 minutes\), a TLS certificate used by internal backend services expired before being rotated, causing disruption to several back-end capabilities. The certificate has been renewed and all affected services are fully operational. **Impact** During the incident window, customers may have experienced: * **Outbound email delivery:** Emails sent from the platform during this window failed to send. * **iPaaS workflow steps:** iPaaS step types within ticket workflows failed to execute. * **Logging gaps:** Logging within the TeamDynamix Work Management application may have gaps during the incident window. **Root Cause** A TLS certificate used for internal service-to-service authentication reached its expiration date before being rotated. The expiration was not surfaced by our existing monitoring in time for the team to act. When the certificate expired, the affected services could no longer authenticate to dependent systems, producing the impact described above. **Resolution** The certificate was renewed and the affected services recovered automatically once trust was re-established. **Preventing Recurrence** We have expanded certificate expiry monitoring and alerting in our observability stack so that alerts trigger well in advance of expiration. We have also audited our existing certificate inventory to confirm no other certificates are at near-term risk. We're sorry for the disruption this caused. If you have questions about your specific environment, please reach out to our support team.

Investigating client-licensed resource issues regarding access to interact with appropriate areas of Projects via the client portal. Client users are unable to add new issues and update tasks on project plans that they've been assigned to.

A fix for the issues surrounding client portal interactions with project content was released last night and confirmed as addressing the problems in full. This is resolved at this point.

We are investigating a delay in webhooks executions that began approximately around 2:14 PM ET. We're taking steps to mitigate the delays as soon as possible.

As of 4:19 PM EST, webhooks are caught back up and processing as expected.