To prevent future incidents similar to the one on June 6, 2024, Zendesk is implementing more robust testing for live messaging conversations. Additionally, they are investigating longer soak times for messaging-specific code changes. These measures aim to ensure that any potential issues are identified and addressed before affecting users.
On June 6, 2024, Zendesk experienced a service incident where users encountered errors when loading messaging tickets. From 22:03 UTC to 22:40 UTC, some Zendesk Support customers saw a 'Couldn’t connect to server' error while updating tickets….
The service incident on June 6, 2024, was caused by a bug in the messaging and omnichannel feature. This bug was introduced during a recent code deployment. As a result, users experienced errors when trying to update tickets and some faced…
The Zendesk service incident on June 6, 2024, was resolved by identifying and rolling back the code change that caused the issue. The team quickly pinpointed the problematic code and reverted it to restore normal functionality. This action helped…
For current system status information about Zendesk, you can check their system status page. This page provides updates and summaries of post-mortem investigations a few days after incidents have ended. If you have further questions, you can also…