Zendesk resolved the Chat Pod 23 server issue by restarting the affected compute capacity instance. This action migrated the service to another stable AWS host, effectively resolving the problem. Additionally, they consulted with their infrastructure partner to confirm the underlying issue. The resolution ensured that there was no data loss, although ongoing chats during the incident may have been dropped prematurely.
On August 1, 2024, a server issue affected Zendesk Chat users on Pod 23. From 12:10 UTC to 12:33 UTC, some customers experienced disconnected chats and were unable to start new ones. The issue was due to an unexpected AWS infrastructure failure…
The root cause of the Zendesk Chat Pod 23 incident was an unexpected AWS infrastructure failure. This failure affected a particular compute capacity instance, leading to disconnected chats and an inability to initiate new ones for some users. The…
There was no data loss during the Zendesk Chat Pod 23 incident. However, ongoing chats for affected accounts may have been dropped prematurely. These chats were recovered and saved, albeit with a time delay. Zendesk assured users that all chat data…
To prevent future incidents like the Chat Pod 23 issue, Zendesk is implementing several remediation items. These include ensuring automatic restart of the LiveChat server if shut down by AWS, updating the alerting system for more accurate…
For current system status information about your Zendesk, you can check out their system status page. This page provides updates and summaries of post-mortem investigations a few days after incidents have ended. If you have additional questions,…