Root Cause of Zendesk Incident on December 3, 2023
What was the root cause of the Zendesk incident on December 3, 2023?
The root cause of the Zendesk incident on December 3, 2023, was a defect in a code deployment. This defect led to a 15-minute period where the database caching facility was unreachable.
This unavailability caused a backlog in the message queue, resulting in 503 errors for customers. Zendesk has identified this issue and is taking steps to prevent similar incidents in the future by adding specific test cases and monitoring alerts.
More related questions
What happened during the Zendesk service incident on December 3, 2023?
On December 3, 2023, some Zendesk Support customers on Pod 28 faced server errors and access issues. This incident lasted from 09:31 to 10:46 UTC and was due to an account-related issue. The problem was caused by a defect in a code deployment that…
How did Zendesk resolve the service incident on December 3, 2023?
Zendesk resolved the service incident on December 3, 2023, by addressing the database caching issue. Once the caching facility became available again, the processing of the service backlog resumed, leading to recovery. The incident was caused by a…
What steps is Zendesk taking to prevent future incidents like the one on December 3, 2023?
To prevent future incidents like the one on December 3, 2023, Zendesk is implementing several remediation items. These include adding a specific test case against the caching timeout logic and setting up a monitor alert to notify when the caching…
How did Zendesk communicate with customers during the December 3, 2023 incident?
During the December 3, 2023 incident, Zendesk acknowledged a lack of communication with customers. They have expressed sincere apologies for this and are investigating the internal process breakdown that prevented timely updates. Zendesk is working…
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.
