Preventive Measures After Zendesk Incident April 24, 2024
What steps did Zendesk take to prevent future incidents like the one on April 24, 2024?
To prevent future incidents similar to the one on April 24, 2024, Zendesk planned several remediation actions. These include reviewing procedures for safely removing the mobile SDK API location and removing specialized routing from systems that have completed rollout.
These steps are part of Zendesk's commitment to improving system reliability and ensuring that similar issues do not occur in the future. By addressing the root cause and implementing preventive measures, Zendesk aims to enhance the stability of its services.
More related questions
What happened during the Zendesk service incident on April 24, 2024?
On April 24, 2024, Zendesk experienced a service incident affecting mobile SDK users. From 13:37 UTC to 16:40 UTC, users encountered errors when trying to initialize or connect to the mobile SDK, which led to an inability to receive messages from…
How was the April 24, 2024, Zendesk service incident resolved?
The service incident on April 24, 2024, was resolved by deploying new code to re-enable the correct configuration. This action addressed the issue caused by the removal of the mobile SDK API from the internal routing gateway. After the deployment,…
What was the root cause of the Zendesk incident on April 24, 2024?
The root cause of the Zendesk incident on April 24, 2024, was a software update that removed the mobile SDK API from the internal routing gateway. Initially, it was believed that this location was not in use, but it was later discovered that a…
How can I find more information about Zendesk's system status?
For current system status information about Zendesk, you can visit their system status page. This page provides updates on any ongoing issues and summaries of post-mortem investigations after incidents have ended. If you have additional questions…
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.
