Is Tines down?

<small>2026-04-17 21:31:00 UTC</small><br /><strong>Operational [<em>Resolved</em>]</strong><br />Action Run performance has been restored to normal levels as of 21:31 UTC. Pending action runs enqueued during the incident have been processed. We apologize gain for any inconvenience this may have caused. If you have any questions, please contact Tines support.<br /><br /><small>2026-04-17 19:23:31 UTC</small><br /><strong>Degraded performance [<em>Monitoring</em>]</strong><br />We have identified and remediated the source of the delayed Action runs. Action runs are beginning to resume running at a normal rate and duration. Next Steps: We are monitoring the results of the remediation and will fully resolve the incident when Action run performance has returned to normal levels.<br /><br /><small>2026-04-17 18:23:34 UTC</small><br /><strong>Degraded performance [<em>Investigating</em>]</strong><br />Our teams are continuing to investigate the cause of and resolve the issue causing delayed action runs. We do not currently have an ETA for resolution. Next Steps: We will provide an update as to the status of this incident as soon as more information is available. Thank you for your patience as we work to restore performance. <br /><br /><small>2026-04-17 15:50:00 UTC</small><br /><strong>Degraded performance [<em>Investigating</em>]</strong><br />Impact: Cloud tenants on US1 Stack Summary: Tenants on the US1 stack may experience delayed action runs beginning approximately 15:50 UTC April 17. Next Steps: Our engineering team is investigating the cause and are working to resolve.

<small>2026-02-25 15:37:44 UTC</small><br /><strong>Operational [<em>Resolved</em>]</strong><br />Status: Resolved Summary: Our engineering team has restored the Tines Image Registry. Customers are now able to pull images as normal. We apologize for any inconvenience this may have caused. If you have any questions, please contact Tines Support.<br /><br /><small>2026-02-25 09:00:00 UTC</small><br /><strong>Problem detected [<em>Resolving</em>]</strong><br />Status: Problem Detected and Resolving Impact: Self-hosted deployments Summary: Beginning approximately 9:00 UTC 2026/02/25, requests Tines Image Registry are currently failing with a 401 status code. Customers attempting to pull images from the registry are unable to do so. Next Steps: Our engineering team has identified the issue and are actively working to resolve.

<small>2026-02-19 21:21:10 UTC</small><br /><strong>Operational [<em>Resolved</em>]</strong><br />We have deployed Tines self-hosted-version 39.1.1 to patch the Sidekiq concurrency issue. Customers running Tines version 39.0.0 or later should upgrade to 39.1.1. Please find the release notes can here: https://www.tines.com/docs/self-hosting/release-notes/#february-19th-2026-39-1-1 We apologize for any impact this may have caused. Please contact Support should you have any questions about or experience any issues with the upgrade.<br /><br /><small>2026-02-19 00:04:53 UTC</small><br /><strong>Problem detected [<em>Resolving</em>]</strong><br />Impact: Customers who have deployed Tines self-hosted version 39.0.0 or greater Summary: Our Engineering team have identified an issue on self hosted deployments running v39.0.0 and v39.1.0 where the amount of workers available to the tenant is not reflective of what is set for the environment variable SIDEKIQ_CONCURRENCY which could impact negatively on action run processing. Workaround: If you are noticing any slower action run processing, setting the environment variable SIDEKIQ_DEFAULT_ACTIONS_QUEUE_CONCURRENCY to match that of the environment variable SIDEKIQ_CONCURRENCY should resolve the issue. Next Steps: We are testing a patch release for versions 39.0.0+ and currently-existing 39.X.X versions will be deprecated. Once the patch is released, customers should upgrade to the patched version.

<small>2026-02-10 22:48:00 UTC</small><br /><strong>Operational [<em>Resolved</em>]</strong><br />Status: Resolved Impact: All cloud stacks Summary: Users were intermittently unable to log in to Tines via https://login.tines.com/, receving a "Page not found" or similar error in the browser. Event processing was unaffected. Resolution: AWS has reported full recovery for the DNS resolution errors for CloudFront distributions. Tines has not observed login DNS errors since 21:57 UTC. We again appreciate your patience and apologize for any inconvenience caused by this incident. Please contact support should you have any questions.<br /><br /><small>2026-02-10 21:46:38 UTC</small><br /><strong>Degraded performance [<em>Identified</em>]</strong><br />Status: Monitoring Impact: All cloud stacks Summary: Users may not be able to log in to Tines via https://login.tines.com/, receving a "Page not found" or similar error in the browser. Event processing is unaffected. Next Steps: An operational issue with AWS CloudFront is resulting in DNS resolution failures. We are continuing to monitor this issue and will provide an update at 22:45 UTC. <br /><br /><small>2026-02-10 20:39:00 UTC</small><br /><strong>Problem detected [<em>Identified</em>]</strong><br />Status: Problem Detected and Investigating Impact: All cloud stacks Summary: Users may not be able to log in to Tines via https://login.tines.com/, receving a "Page not found" or similar error in the browser. Event processing is unaffected. Next Steps: Our engineering team is investigating the cause and are working to resolve. We apologize for any inconvenience this may cause.

<small>2026-02-25 20:06:05 UTC</small><br /><strong>Operational [<em>Resolved</em>]</strong><br />Thank you for your patience as we continue enhancing the credential flow experience for self-hosted customers with functionality to streamline credential management. In the meantime, credentials can still be created manually. If you would like assistance with manual credential creation, our support team is happy to help. We will share an update with all self-hosted customers as soon as the enhanced credential flow capability becomes available.<br /><br /><small>2026-02-19 16:19:57 UTC</small><br /><strong>Problem detected [<em>Resolving</em>]</strong><br />Status: We have identified the cause of the issue and are finalizing a resolution. Impact: All self-hosted deployments. Summary: Beginning approximately 07:00 UTC 2026/02/07, users may be unable to create new credentials using the Connect Flow. Existing credentials and event processing are unaffected. Workaround Credentials can be created manually in Tines. You can follow the instructions found here https://www.tines.com/docs/credentials/ Next Steps: Our engineering team is finalizing a fix for the issue. If you need any assistance with creating credentials or any other part of your workflow, please contact support. We appreciate your patience and apologize for any inconvenience caused. A further update will be provided next week.<br /><br /><small>2026-02-13 11:28:12 UTC</small><br /><strong>Problem detected [<em>Identified</em>]</strong><br />Status: We have identified the cause of the issue and are working on a resolution. Impact: All self-hosted deployments. Summary: Beginning approximately 07:00 UTC 2026/02/07, users may be unable to create new credentials using the Connect Flow. Existing credentials and event processing are unaffected. Workaround Credentials can be created manually in Tines. You can follow the instructions found here https://www.tines.com/docs/credentials/ Next Steps: Our engineering team is working to resolve the issue. If you need any assistance with creating credentials or any other part of your workflow, please contact support. We appreciate your patience and apologize for any inconvenience caused. A further update will be provided next week. <br /><br /><small>2026-02-10 18:00:23 UTC</small><br /><strong>Problem detected [<em>Investigating</em>]</strong><br />Status: Problem Detected and Investigating Impact: All self-hosted deployments. Summary: Beginning approximately 07:00 UTC 2026/02/07, users may be unable to create new credentials using the Connect Flow. Existing credentials and event processing are unaffected. Workaround Credentials can be created manually in Tines. You can follow the instructions found here https://www.tines.com/docs/credentials/ Next Steps: Our engineering team is working to resolve the issue. We appreciate your patience and apologize for any inconvenience caused. <br /><br /><small>2026-02-07 07:00:00 UTC</small><br /><strong>Problem detected [<em>Identified</em>]</strong><br />Status: Problem Detected and Investigating Impact: All Tines cloud stacks and self-hosted deployments. Summary: Beginning approximately 07:00 UTC 2026/02/07, users may be unable to create new credentials using the Connect Flow. Existing credentials and event processing are unaffected. Next Steps: Our engineering team is working to to resolve the issue.