Tray.io Outage History

Tray.io is up right now

Pingoru has recorded 52 incidents for Tray.io: 22 in the last 12 months and 4 in the last 90 days.

Source: status.tray.io

52incidents recorded
22last 12 months
4last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Tray.io 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 202621 of 592 (0%)

Incidents, newest first

Notice March 11, 2025 Debug Retry, Replay, Stop Button Non-functional 1h 54m Workflow Builder Logs

Started Mar 11, 2025, 01:39 PM UTC· resolved Mar 11, 2025, 03:33 PM UTC

  1. resolved Mar 11, 2025, 04:21 PM UTC

    This incident has been resolved and all our systems are operational. The retry step, replay execution, and stop execution buttons within the debug log were non-functional from 13:39 to 15:33 GMT in all regions (US, EU, & AP). Customers may have observed pressing the retry, replay, or stop button on individual logs did not have an effect. Our engineers identified the root cause and have fixed this 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]. Thank you for your patience and understanding.

Read the full incident report →

Minor January 31, 2025 Degraded Application Performance — Execution Logs 54m Workflow Execution

Started Jan 31, 2025, 12:54 AM UTC· resolved Jan 31, 2025, 01:48 AM UTC

  1. investigating Jan 31, 2025, 12:54 AM UTC

    We are currently investigating an issue where some new executions are not appearing in the workflow logs in the US region. Execution steps are still running, but their logs may not appear. If you have any questions or concerns, please feel free to reach out to [email protected].

  2. resolved Jan 31, 2025, 01:48 AM UTC

    This incident has been resolved, and all our systems are operational. Any missing logs should now appear as expected. 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 →

Notice January 21, 2025 Degraded Application Performance Workflow Imports – Workflow Execution

Started Jan 21, 2025, 10:13 PM UTC· resolved Jan 21, 2025, 10:13 PM UTC

  1. resolved Jan 21, 2025, 10:13 PM UTC

    Between 12:32 PM and 7:09 PM, users may have experienced issues with the ability to import 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 January 13, 2025 Degraded Application Performance - Call Connector API –

Started Jan 13, 2025, 12:00 PM UTC· resolved Jan 13, 2025, 12:00 PM UTC

  1. resolved Jan 14, 2025, 02:10 PM UTC

    Between 12:09 PM and 12:35 PM, users may have experienced the Call Connector API failing and retrying, causing slight delays in their workflow executions. 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 →

Major December 6, 2024 Connector Authentication Refresh Performance 16m Other

Started Dec 06, 2024, 06:04 PM UTC· resolved Dec 06, 2024, 06:20 PM UTC

  1. monitoring Dec 06, 2024, 06:04 PM UTC

    We experienced an issue with several connectors being unable to refresh their authentications. Our engineering teams have applied a fix 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.

  2. resolved Dec 06, 2024, 06:20 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 →

Notice November 27, 2024 Degraded Performance of the Data Storage Connector – Workflow Execution, Other

Started Nov 27, 2024, 01:15 PM UTC· resolved Nov 27, 2024, 01:15 PM UTC

  1. resolved Nov 27, 2024, 01:15 PM UTC

    Between 11:55 AM and 12:30 PM (UTC), users may have experienced Data Storage steps failing and retrying, causing slight delays in their workflow executions. 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 →

Notice November 22, 2024 Momentary Outage of Tray APIs 3m Workflow Execution, Workflow Builder API, Embedded API, Connectors API and 1 more

Started Nov 22, 2024, 04:12 PM UTC· resolved Nov 22, 2024, 04:15 PM UTC

  1. investigating Nov 22, 2024, 04:12 PM UTC

    There was a 3-minute outage of Tray APIs between 15:47 and 15:50 UTC for US instances of Tray. Customers may have noticed workflow delays and delays in changes made working with the workflow builder. The issue is now resolved. We are currently investigating an issue that is caused unexpected behaviours. If you have any questions or concerns, please feel free to reach out to [email protected].

  2. resolved Nov 22, 2024, 04:15 PM UTC

    This incident has been resolved and all our systems are operational. There was a 3-minute outage of Tray APIs between 15:47 and 15:50 UTC for US instances of Tray. Customers may have noticed workflow delays and delays in changes made working with the workflow builder. 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 →