Following the Zendesk incident on January 24, 2024, several remediation steps are being taken to prevent future occurrences.
These steps include reviewing recovery procedures and resiliency, increasing application host sizes, and updating health checks to ensure latency remains below the required threshold. These measures are either in progress or scheduled to enhance the system's robustness.
On January 24, 2024, Zendesk experienced a service incident affecting Sunshine Conversations. Between 17:35 and 17:50 UTC, customers across all pods encountered increased message latency and 5xx level errors for both incoming and outbound messages….
The message latency and errors during the Zendesk incident on January 24, 2024, were caused by latency introduced during application server restarts. These restarts were part of the recovery process for an earlier service issue. As the servers…
The Zendesk service issue on January 24, 2024, was resolved as the application servers completed their restarts. This self-resolution occurred because the latency introduced during the server restarts was temporary, and once the restarts were…
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, usually posted a few days after an incident has ended. If you have further…