Preventing Future Zendesk Incidents: May 2, 2024 Lessons
What steps is Zendesk taking to prevent future incidents like the one on May 2, 2024?
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 capacity to handle traffic during updates, and adding new checks to monitor service health more effectively.
Additionally, Zendesk is working on better coordination between different components of the service infrastructure and reviewing the impact on all services to prevent similar issues in the future.
More related questions
What happened during the Zendesk service incident on May 2, 2024?
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…
How did Zendesk resolve the service incident on May 2, 2024?
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…
What was the root cause of the Zendesk service incident on May 2, 2024?
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,…
Which Zendesk products were affected during the May 2, 2024 incident?
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….
How long did the Zendesk service incident on May 2, 2024 last?
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…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
