Is Tray.io down?

We're currently investigating an issue affecting login for users logging in via email verification. Our engineering team is looking into it and working to restore normal service as quickly as possible. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

We've identified the cause of the issue. Our engineering team is working on a fix and we'll provide a further update shortly. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

Our engineering team is continuing to work on a fix. In the meantime, affected users can log in via the alternative login page for their region as a workaround: US: https://app.tray.io/v2/login EU: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

We've applied a fix and login should now be working as expected. We're monitoring the situation closely to ensure the issue is fully resolved. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

This incident has been resolved and login is now working as expected. Thank you for your patience. If you have any further questions, please feel free to reach out to [email protected].

On July 13, 2026, starting at 15:20 UTC, Gmail authentications within the US region may encounter retries when refreshing the token, but should eventually succeed. We are currently investigating. Thank you for your patience and understanding. If you have any questions or concerns, please feel free to reach out to [email protected].

Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

During the investigation, we isolated the impact couple of customers and reached out to those customers. If you did not receive a message from us related to this incident, it is highly unlikely that your organization was impacted by this incident. We have a identified the potential cause and are continuing to investigate. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

On July 13, 2026, from 15:20 to 19:36 UTC, Gmail authentications within the US region may have encountered token refresh retries that eventually succeeded. The impact was isolated to two customers and we have reached out to those customers. If you did not receive a message related to this incident, your organization should not have been affected. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

Starting 7:00 AM UTC on Thursday, July 2, 2026, some customers in the US region may be experiencing issues with scheduled triggers not firing, which is impacting workflow execution. Our team is currently investigating the root cause and working towards a resolution. We will provide further updates as more information becomes available. We apologise for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

We have identified the issue causing scheduled triggers not to fire, impacting workflow execution in the US region. Our team is currently applying a fix and monitoring the results closely. We will provide further updates as more information becomes available.

The fix for the scheduled trigger issue has now taken effect, and all delayed workflow executions have caught up. Our systems have been operating normally since 7:50 AM UTC. We are continuing to monitor the situation closely to ensure stability.

This incident has now been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

Users may be experiencing issues related to project versions across all regions. Our engineering team is currently investigating the issue and working toward a resolution. We apologise for any inconvenience this incident may have caused.

This incident has been resolved.

On 6 June 2026, some customers experienced Salesforce authentication failures, causing workflow disruptions. This was due to a 30-day refresh token TTL introduced on 7 May 2026 to meet new Salesforce security requirements. Access tokens used continuously for over 30 days had their refresh tokens expire, rendering them unusable. The issue has been resolved. Affected customers were required to re-authenticate their Salesforce connection to restore functionality. We are implementing a proactive background refresh process for Salesforce authentications to ensure tokens are refreshed before the 30-day expiry, regardless of access token usage. We apologize for any inconvenience this incident may have caused. If you have any questions or need additional details, please feel free to reach out to [email protected].