The Zendesk service incident on May 2, 2024, lasted for approximately 50 minutes. It began at 13:35 UTC and was resolved by 14:25 UTC.
During this time, customers experienced slow performance and internal server errors across multiple products and Pods. The issue was resolved by rerouting internal traffic, restoring full service by the end of the incident.
On May 2, 2024, Zendesk experienced a service incident that affected multiple products across all Pods. From 13:35 UTC to 14:25 UTC, customers faced slow performance and internal server errors. The incident was particularly impactful for users on…
Zendesk resolved the service incident on May 2, 2024, by rerouting internal traffic to bypass the affected infrastructure. This action restored full service by 14:25 UTC. The issue stemmed from a glitch in the service update process, which reduced…
The root cause of the Zendesk service incident on May 2, 2024, was a glitch in the service update process. This glitch led to some parts of the infrastructure not being ready to handle traffic, resulting in reduced capacity. To address this,…
To prevent future incidents like the one on May 2, 2024, Zendesk is implementing several remediation items. These include improving the infrastructure update process to detect and address issues before they affect customers, enhancing system…
During the May 2, 2024 incident, several Zendesk products were affected, particularly for customers on Pod 23. These products included the Support agent interface, Sunshine Conversations Messaging, Chat, Talk, Explore, Sell, and Guide….