Historial de interrupciones de Kayako

We are currently investigating reported slowness when creating or replying to tickets.

We are continuing to investigate this issue.

The incident has been resolved, and we are monitoring the situation

The issue causing elevated response times for ticket creation and reply actions has been resolved. Our Infrastructure team has completed the necessary mitigation steps, and we are seeing response times return to expected levels. We will continue to monitor the platform to ensure stability. Thank you for your patience while we worked through this issue.

AWS has confirmed “increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region” with a severity labelled “Degraded”. This affects Kayako instances and you may experience issues loading your Help Centers or interacting with the Help Center.

AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.

We have been made aware of an issue related to Slow performance on some specific Kayako Instances. We are currently investigating this and will get back to you as soon as we have more information to share.

We are continuing to investigate this issue.

We have identified a probable root cause of the issue affecting the performance on some specific Kayako instances. Our team is actively working on resolving it to restore optimal functionality as quickly as possible. Thank you for your patience and understanding. We will provide further updates as soon as more information becomes available.

We believe the issue is currently resolved, but we are still actively monitoring the servers. The customers are advised to check their instances and confirm that they are fully operational.

The issue has been resolved.

We have been made aware of an issue where the Triggers page is not loading as expected. We are presently investigating this and will get back to you as soon as we have more information to share.

We are continuing to investigate this issue.

We have identified the root cause of this issue and are currently rolling a fix to all affected customers.

A fix has been rolled out to all customers and the issue should no longer persist. If you still face any problems, please let us know so that we may assist you further.