Tray.ai Outage History

Tray.ai is up right now

Pingoru has recorded 53 incidents for Tray.ai: 23 in the last 12 months and 5 in the last 90 days.

Source: status.tray.ai

53incidents recorded
23last 12 months
5last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Tray.ai in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610 of 720 (0%)
May 202624 of 744 (1%)
June 202630 of 720 (0%)
July 202636 of 744 (1%)
August 202618 of 744 (1%)
September 202611 of 720 (0%)
October 202631 of 523 (0%)

Incidents, newest first

Notice October 19, 2026 Degraded Application Performance - Helix Deployments 40m Helix

Started Oct 19, 2026, 04:50 PM UTC· resolved Oct 19, 2026, 05:30 PM UTC

  1. resolved Oct 19, 2026, 06:49 PM UTC

    Between 16:50 and 17:30 UTC, some users may have experienced failures when deploying Helix projects. Deployments failed with an "Internal server error" (HTTP 500), but existing live deployments were unaffected. The issue has been resolved, and deployments are working normally. We apologize 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 →

Notice October 17, 2026 Degraded Application Performance –

Started Oct 17, 2026, 01:46 PM UTC· resolved Oct 17, 2026, 01:46 PM UTC

  1. resolved Oct 17, 2026, 04:02 PM UTC

    Between 13:15 and 13:40 UTC, some users in the US region may have experienced workflow execution delays of up to 30 minutes. All executions have since been processed, and no data was lost. 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]. The 13:15 UTC start comes from the alert, which fired at 09:17 ET. If Sam can see that delays started earlier in the queue metrics, use that time instead.

Read the full incident report →

Minor September 30, 2026 Degraded Application Performance - Send Email Connector 1h 21m Other

Started Sep 30, 2026, 02:43 PM UTC· resolved Sep 30, 2026, 04:04 PM UTC

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

  2. identified Sep 30, 2026, 03:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 30, 2026, 03:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. 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 8h

Started Aug 10, 2026, 11:00 AM UTC· resolved Aug 10, 2026, 07:00 PM UTC

  1. 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 2h 42m Workflow Builder App

Started Jul 16, 2026, 12:06 PM UTC· resolved Jul 16, 2026, 02:49 PM UTC

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

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

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

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

  5. 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 →

Major July 2, 2026 Scheduled Trigger Degraded Performance 45m Workflow Execution

Started Jul 02, 2026, 08:06 AM UTC· resolved Jul 02, 2026, 08:51 AM UTC

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

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

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

  4. 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 39s Workflow Execution, Insights, Usage and Logs

Started Jun 18, 2026, 04:12 PM UTC· resolved Jun 18, 2026, 04:13 PM UTC

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

  2. 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 –

Started Jun 06, 2026, 04:00 PM UTC· resolved Jun 06, 2026, 04:00 PM UTC

  1. 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 –

Started Jun 03, 2026, 04:45 PM UTC· resolved Jun 03, 2026, 04:45 PM UTC

  1. 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 –

Started Apr 28, 2026, 09:30 AM UTC· resolved Apr 28, 2026, 09:30 AM UTC

  1. 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 1h 21m Other

Started Jan 15, 2026, 10:36 PM UTC· resolved Jan 15, 2026, 11:58 PM UTC

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

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

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

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

  5. 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 41m Merlin Agent Builder

Started Jan 06, 2026, 10:08 AM UTC· resolved Jan 06, 2026, 10:49 AM UTC

  1. 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 18m Merlin Agent Builder

Started Jan 05, 2026, 06:37 AM UTC· resolved Jan 05, 2026, 06:55 AM UTC

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

  2. 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 59m Workflow Execution, Connectors API

Started Nov 25, 2025, 04:21 AM UTC· resolved Nov 25, 2025, 05:20 AM UTC

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

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

  3. 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 18h 45m Other

Started Nov 10, 2025, 04:19 PM UTC· resolved Nov 11, 2025, 11:04 AM UTC

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

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

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

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

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

  6. 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 3h 29m Insights, Usage and Logs

Started Oct 20, 2025, 05:58 PM UTC· resolved Oct 20, 2025, 09:27 PM UTC

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

  2. 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 59m Workflow Execution, Workflow Triggers

Started Oct 20, 2025, 09:36 AM UTC· resolved Oct 20, 2025, 10:36 AM UTC

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

  2. resolved Oct 20, 2025, 10:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 1, 2025 Degraded Workflow Execution Performance - APAC 55m Workflow Execution

Started Aug 01, 2025, 01:41 PM UTC· resolved Aug 01, 2025, 02:36 PM UTC

  1. investigating Aug 01, 2025, 01:41 PM UTC

    At 14:22 PM BST, users may have experienced issues with the workflow executions in the APAC region. 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].

  2. monitoring Aug 01, 2025, 02:22 PM UTC

    Our engineering teams have applied a fix at 15:05 and are currently monitoring the results. 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.

  3. monitoring Aug 01, 2025, 02:23 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 01, 2025, 02:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2025 Degraded Application Performance - US 28m

Started Jun 25, 2025, 10:00 AM UTC· resolved Jun 25, 2025, 10:28 AM UTC

  1. resolved Jun 25, 2025, 11:31 AM UTC

    Between 11:10 AM BST and 11:28 AM BST, users in the US region may have experienced delays of up to approximately 10 minutes when processing trigger updates to workflows, initializing new workflows, or processing changes to existing triggers. We apologize 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 June 18, 2025 Degraded Application Performance EU On-Prem 8m Workflow Execution

Started Jun 18, 2025, 02:55 PM UTC· resolved Jun 18, 2025, 03:04 PM UTC

  1. investigating Jun 18, 2025, 02:55 PM UTC

    Beginning at 14:40 GMT, EU customers may have begun experiencing issues with executions of their on-prem connectors. We are investigating at this time and will continue to update the status here. Please reach out to [email protected] if you have any questions or concerns at this time.

  2. resolved Jun 18, 2025, 03:04 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 June 12, 2025 Degraded Application Performance - Gmail Trigger EU 54m Workflow Execution, Workflow Triggers

Started Jun 12, 2025, 06:27 PM UTC· resolved Jun 12, 2025, 07:22 PM UTC

  1. investigating Jun 12, 2025, 06:27 PM UTC

    Beginning at 18:11 GMT, users may have begun experiencing issues with the Gmail trigger. Customers on the EU server may have had difficulties logging in to the Tray application as well. We are currently investigating the source and will continue to update here. We apologize for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to [email protected].

  2. resolved Jun 12, 2025, 07:22 PM UTC

    This incident has been resolved and all our systems are operational. We apologize 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 10, 2025 Degraded Application Performance - On-prem EU 25m Workflow Execution, Other

Started Jun 10, 2025, 03:20 PM UTC· resolved Jun 10, 2025, 03:46 PM UTC

  1. identified Jun 10, 2025, 03:20 PM UTC

    We have recognized failures on on-prem connectors in the EU environment. We are investigating the cause and will work towards resolution. Please reach out to support if you have any questions or concerns about this incident.

  2. resolved Jun 10, 2025, 03:46 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 June 10, 2025 Degraded On-Prem Connector Performance 11m Other

Started Jun 10, 2025, 02:56 PM UTC· resolved Jun 10, 2025, 03:07 PM UTC

  1. monitoring Jun 10, 2025, 02:56 PM UTC

    We encountered an error with on-prem connector executions at 14:31 GMT. Customers using on-prem connections may have noticed a disruption in executions for those connectors. Our engineering teams have applied a fix and are currently monitoring the results. We apologize 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.

  2. resolved Jun 10, 2025, 03:07 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 March 27, 2025 Degraded Performance of Connectors 2h 41m

Started Mar 27, 2025, 07:15 PM UTC· resolved Mar 27, 2025, 09:56 PM UTC

  1. resolved Mar 27, 2025, 10:35 PM UTC

    Our engineers have identified and resolved an issue that affected a small subset of connectors, leading to degraded performance between 19:15 and 21:56 GMT (12:15 to 14:56 PDT). During this time, some workflows using these connectors may have failed. The issue has now been fully resolved, and all services are operating normally. 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 →

Minor March 11, 2025 Degraded Application Performance in EU 32m Workflow Execution

Started Mar 11, 2025, 02:22 PM UTC· resolved Mar 11, 2025, 02:55 PM UTC

  1. investigating Mar 11, 2025, 02:39 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.

  2. monitoring Mar 11, 2025, 02:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 11, 2025, 02:55 PM UTC

    Workflow executions on the EU platform may have experienced some degraded performance between 14:22 GMT and 14:56 GMT. This incident has been resolved, and all our systems are operational.

Read the full incident report →