Tray.io Outage History

Tray.io had 16 outages in the last 2 years totaling 33h 37m of downtime — averaging 0.7 incidents per month.

There were 16 Tray.io outages since October 20, 2025 totaling 33h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tray.io

Minor September 30, 2026

Degraded Application Performance - Send Email Connector

Detected by Pingoru: Sep 30, 2026, 02:43 PM UTC
Resolved: Sep 30, 2026, 04:04 PM UTC
Duration: 1h 21m

Affected: Other

Timeline · 4 updates

investigating Sep 30, 2026, 02:43 PM UTC

Starting from 14:08 UTC, users may have experienced issues with the Send Email connector in the US region. Our engineers are investigating the issue. 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].
identified Sep 30, 2026, 03:03 PM UTC

The issue has been identified and a fix is being implemented.
monitoring Sep 30, 2026, 03:14 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Sep 30, 2026, 04:04 PM UTC

This incident has been resolved.

Read the full incident report →

Notice August 10, 2026

Billing and Usage Temporarily Unavailable

Detected by Pingoru: Aug 10, 2026, 11:00 AM UTC
Resolved: Aug 10, 2026, 11:00 AM UTC
Duration: —

Timeline · 1 update

resolved Aug 10, 2026, 07:26 PM UTC

Due to a degradation of application performance, the Billing and Usage page was temporarily unavailable for all regions between approximately 11:00 UTC and 19:00 UTC. Billing and usage has been restored to normal functionality. We apologize for any inconvenience this 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.

Read the full incident report →

Major July 16, 2026

Issues Logging into Tray Application

Detected by Pingoru: Jul 16, 2026, 12:06 PM UTC
Resolved: Jul 16, 2026, 02:49 PM UTC
Duration: 2h 42m

Affected: Workflow Builder App

Timeline · 5 updates

investigating Jul 16, 2026, 12:06 PM UTC

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].
identified Jul 16, 2026, 12:28 PM UTC

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].
identified Jul 16, 2026, 01:48 PM UTC

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].
monitoring Jul 16, 2026, 02:33 PM UTC

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].
resolved Jul 16, 2026, 02:49 PM UTC

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].

Read the full incident report →

Minor July 13, 2026

Degraded Application Performance

Detected by Pingoru: Jul 13, 2026, 07:39 PM UTC
Resolved: Jul 13, 2026, 10:32 PM UTC
Duration: 2h 53m

Affected: Other

Timeline · 4 updates

investigating Jul 13, 2026, 07:39 PM UTC

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].
investigating Jul 13, 2026, 09:01 PM UTC

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.
identified Jul 13, 2026, 09:55 PM UTC

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.
resolved Jul 13, 2026, 10:32 PM UTC

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.

Read the full incident report →

Major July 2, 2026

Scheduled Trigger Degraded Performance

Detected by Pingoru: Jul 02, 2026, 08:06 AM UTC
Resolved: Jul 02, 2026, 08:51 AM UTC
Duration: 45m

Affected: Workflow Execution

Timeline · 4 updates

investigating Jul 02, 2026, 08:06 AM UTC

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.
identified Jul 02, 2026, 08:09 AM UTC

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.
monitoring Jul 02, 2026, 08:11 AM UTC

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.
resolved Jul 02, 2026, 08:51 AM UTC

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.

Read the full incident report →

Minor June 18, 2026

Degraded Application Performance - Project Versions

Detected by Pingoru: Jun 18, 2026, 04:12 PM UTC
Resolved: Jun 18, 2026, 04:13 PM UTC
Duration: 39s

Affected: Workflow ExecutionInsights, Usage and Logs

Timeline · 2 updates

investigating Jun 18, 2026, 04:12 PM UTC

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.
resolved Jun 18, 2026, 04:13 PM UTC

This incident has been resolved.

Read the full incident report →

Minor June 6, 2026

Degraded Application Performance - Salesforce Connector

Detected by Pingoru: Jun 06, 2026, 04:00 PM UTC
Resolved: Jun 06, 2026, 04:00 PM UTC
Duration: —

Timeline · 1 update

resolved Jun 12, 2026, 10:29 PM UTC

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].

Read the full incident report →

Minor June 3, 2026

Degraded Application Performance Creating Data Tables and Vector Tables

Detected by Pingoru: Jun 03, 2026, 04:45 PM UTC
Resolved: Jun 03, 2026, 04:45 PM UTC
Duration: —

Timeline · 1 update

resolved Jun 03, 2026, 05:52 PM UTC

There was a span of about 10 to 15 minutes where customers may have experienced slowness or failures when creating or importing Data Tables or Vector Tables in Tray. Our engineering team has identified the root cause, resolved the incident and have restored performance of the affected services. For any users who may have experienced this degradation in performance, you may have to retry creating or importing the affected Data Table or Vector Table. If you have any questions or concerns, please reach out to to [email protected]. Thank you for your patience and understanding.

Read the full incident report →

Notice April 28, 2026

Degradation in Service Causing Webhook Requests to Timeout

Detected by Pingoru: Apr 28, 2026, 09:30 AM UTC
Resolved: Apr 28, 2026, 09:30 AM UTC
Duration: —

Timeline · 1 update

resolved Apr 30, 2026, 04:52 PM UTC

On April 28th at approximately 09:30 AM UTC, there was a degradation in service that caused requests to Tray webhook workflow endpoints to timeout or return a 504 status. Workflows in the Tray platform will appear to have completed successfully even though responses to the client were never sent. Our engineering teams have identified the issue and resolved the root cause as of April 30th at 02:43 AM UTC. We will continue to monitor performance of the webhook workflows and ensure their reliability. If you have any questions, feel free to reach out to [email protected]

Read the full incident report →

Major January 15, 2026

Office 365 Authentication Issue

Detected by Pingoru: Jan 15, 2026, 10:36 PM UTC
Resolved: Jan 15, 2026, 11:58 PM UTC
Duration: 1h 21m

Affected: Other

Timeline · 5 updates

investigating Jan 15, 2026, 10:36 PM UTC

Starting from January 14, 2026, users who have Office 365 authentications created using the Tray Production OAuth app may have seen authentications fail and are unable to re-authenticate. 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].
investigating Jan 15, 2026, 11:14 PM UTC

We have identified the issue and our engineering teams are investigating a potential resolution. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to [email protected].
investigating Jan 15, 2026, 11:44 PM UTC

Our engineers have deployed a potential fix. We are currently monitoring to see if the issue resolves. Thank you for your patience and understanding. 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].
monitoring Jan 15, 2026, 11:45 PM UTC

On January 14, 2026 at 2:42:50 PM to January 15, 2026 at 11:31:03 PM UTC, users who have Office 365 authentications created using the Tray Production OAuth app may have seen authentications fail and are unable to re-authenticate. 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].
resolved Jan 15, 2026, 11:58 PM UTC

This incident has 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.

Read the full incident report →

Minor January 6, 2026

Degraded Performance - Merlin Agent Builder

Detected by Pingoru: Jan 06, 2026, 11:07 AM UTC
Resolved: Jan 06, 2026, 11:07 AM UTC
Duration: —

Affected: Merlin Agent Builder

Timeline · 1 update

resolved Jan 06, 2026, 11:07 AM UTC

Between 10:08 AM UTC and 10:49 AM UTC, some users may have encountered errors when using the Tray Native AI model within Merlin Agent Builder workflows. Other models were unaffected. The issue has been resolved, and services are now operating normally. 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].

Read the full incident report →

Minor January 5, 2026

AP Region -- Degraded Performance of Merlin Agent workflows

Detected by Pingoru: Jan 05, 2026, 06:37 AM UTC
Resolved: Jan 05, 2026, 06:55 AM UTC
Duration: 18m

Affected: Merlin Agent Builder

Timeline · 2 updates

investigating Jan 05, 2026, 06:37 AM UTC

We are currently investigating an issue affecting Merlin Agent workflows from around 5:00 AM UTC. AP instance users may notice 500 errors in Merlin Agent workflows. We apologise for any inconvenience this incident 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.
resolved Jan 05, 2026, 06:55 AM UTC

Between 05:00 - 05:55 UTC, AP Instance customers may have noticed errors in Merlin Agent workflows. 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].

Read the full incident report →

Minor November 25, 2025

Workflow Execution and CAPI Performance Degraded

Detected by Pingoru: Nov 25, 2025, 04:21 AM UTC
Resolved: Nov 25, 2025, 05:20 AM UTC
Duration: 59m

Affected: Workflow ExecutionConnectors API

Timeline · 3 updates

investigating Nov 25, 2025, 04:21 AM UTC

We are currently investigating an issue affecting workflow step execution and CAPI that started at around 3:50 AM UTC. US instance users may notice poor performance, including slow connector executions and sporadic connector failures. 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.
monitoring Nov 25, 2025, 05:04 AM UTC

We are actively monitoring the fix implemented for this issue. Users may still experience degraded performance resulting in slow connector executions. We thank you for your patience and 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].
resolved Nov 25, 2025, 05:20 AM UTC

The incident is resolved and executions should be returned to normal. We thank you for your patience and 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].

Read the full incident report →

Major November 10, 2025

Send Email Connector Degraded Performance

Detected by Pingoru: Nov 10, 2025, 04:19 PM UTC
Resolved: Nov 11, 2025, 11:04 AM UTC
Duration: 18h 45m

Affected: Other

Timeline · 6 updates

monitoring Nov 10, 2025, 04:19 PM UTC

An issue is ongoing since November, 8 2025, 12:04PM BST. US instance users may have noticed the Send Email connector versions 3.0 and below may have appeared to execute successfully, however emails may have not actually been sent. A workaround for this issue is to upgrade to version 4.1 of this connector. We have identified the issue with connector version 3.0 and below and are currently investigating a potential resolution. 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.
identified Nov 10, 2025, 05:21 PM UTC

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.
identified Nov 10, 2025, 06:24 PM UTC

Our engineering teams have also identified the services involving reset password emails, adding new users emails and notification emails are also affected. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.
identified Nov 10, 2025, 09:46 PM UTC

We are currently awaiting a response from a third-party service to implement a potential solution. We thank you for your patience and 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].
monitoring Nov 11, 2025, 09:57 AM UTC

We are actively monitoring the fix implemented for this issue. We thank you for your patience and 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].
resolved Nov 11, 2025, 11:04 AM UTC

This incident is resolved, users are now able to receive password reset, new user invites and notification emails. We also recommend any users still using the older version of Send Email connector to upgrade to the latest version (4.1) as soon as possible. We thank you for your patience and 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].

Read the full incident report →

Minor October 20, 2025

Degraded Application Performance Log Streaming Logs

Detected by Pingoru: Oct 20, 2025, 05:58 PM UTC
Resolved: Oct 20, 2025, 09:27 PM UTC
Duration: 3h 29m

Affected: Insights, Usage and Logs

Timeline · 2 updates

monitoring Oct 20, 2025, 05:58 PM UTC

Starting on October 17, 2025 at 2:00 pm EST, US Instances users may have experienced delays in receiving log streaming logs. Our engineering team has implemented a fix and are currently monitoring the progress. 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].
resolved Oct 20, 2025, 09:27 PM UTC

This incident has 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.

Read the full incident report →

Minor October 20, 2025

Degraded Slack Trigger Performance

Detected by Pingoru: Oct 20, 2025, 09:36 AM UTC
Resolved: Oct 20, 2025, 10:36 AM UTC
Duration: 59m

Affected: Workflow ExecutionWorkflow Triggers

Timeline · 2 updates

identified Oct 20, 2025, 09:36 AM UTC

There are ongoing issues with the Slack application and platform. Due to this issue, users may also experience delays with the Slack Trigger within Tray.ai. 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.
resolved Oct 20, 2025, 10:36 AM UTC

This incident has been resolved.

Read the full incident report →