Zendesk is taking several steps to prevent future incidents similar to the one on March 5, 2024. These include improving CDN vendor monitoring and alerting, as well as reviewing internet resilience monitors.
These measures aim to enhance the detection and resolution of similar issues in the future, ensuring a more reliable service for Zendesk users.
On March 5, 2024, Zendesk experienced a service incident affecting some users. Between 1:53 AM and 2:12 AM UTC, customers on pods 13 and 20 faced slow connection speeds or error messages due to networking issues with our CDN vendor. The issue was…
The service issue on March 5, 2024, was resolved by rerouting traffic. Our CDN vendor rerouted a large volume of traffic to mitigate the issue, which was caused by a bad transit in Portland leading to congestion. The problem was resolved at 2:12 AM…
The root cause of the Zendesk service incident on March 5, 2024, was a networking issue. Specifically, customers using Argo Smart Routing through Portland experienced increased failure rates when our CDN vendor disabled a bad transit, causing…
During the Zendesk service issue on March 5, 2024, users experienced several symptoms. These included green error screens, message ticket loading issues, and general slowness when loading pages. These issues were reported by customers on pods 13…
For more information about the Zendesk service incident on March 5, 2024, you can check the system status page. The summary of the post-mortem investigation is usually posted there a few days after the incident has ended. If you have additional…