Tray.ai had 31 outages in the last 2 years totaling 4h 29m of downtime — averaging 1.3 incidents per month.
There were 31 Tray.ai outages since June 7, 2024 totaling 4h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.
We experienced elevated latency affecting the acceptance of all triggers into Tray between 10:37 AM (BST) and 11:02 AM. The issue was swiftly identified and resolved, and normal service resumed. We apologize for any inconvenience this incident may have caused. Thank you for your understanding.
We are currently investigating an issue causing delays in new workflow trigger executions. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at [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.
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.
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.
We are currently investigating an issue causing delays in workflow executions. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at [email protected].
We are continuing to investigate the issue which is causing delays in workflow triggers specifically.
This incident has been resolved, and all our systems are operational. During this incident, short delays in workflow triggers were experienced from 6pm UTC to 6:54pm UTC in the US region. Thank you for your understanding and cooperation during this brief disruption. We appreciate your continued support as we strive to maintain the highest standards of service. If you have any questions or concerns, please feel free to reach out to [email protected].
We are currently investigating an issue which is causing unexpected behaviours with CSV editor connector across all our regions. If you have any questions or concerns, please feel free to reach out to [email protected].
The issue has been identified and we are currently working on a fix to resolve this issue. We are very sorry for any inconvenience this incident may cause.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. 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.
We experienced a brief period of service degradation with the Trigger API between 15:52 and 16:08 (UTC). During this time, users may have encountered delays in processing their Trigger API events. The issue has been resolved, and the service is now operating normally. We apologize for any inconvenience this may have caused. Your satisfaction is important to us, and we appreciate your understanding and patience. If you have any questions or concerns, please contact our support team at [email protected].
We are aware of the service degradation that occurred between 03:18 and 04:46 (UTC +1). During this period, workflow execution steps in the AP data region experienced minor delays due to repeated attempts at execution. All executions were eventually successful. Customers in this region may have noticed these delays and temporary inability to edit workflows. We have now recovered, and workflows are operating normally. We apologize for any inconvenience caused. If you have any questions or concerns, please reach out to us at [email protected].