Preventive Measures for Future Tymeshift Incidents
What steps did Zendesk take to prevent future Tymeshift incidents?
To prevent future Tymeshift incidents, Zendesk has scheduled a global increase of app resources for the service. This is in addition to the immediate action of increasing backend resources during the incident on April 19, 2024. These steps aim to handle increased usage more effectively and prevent similar issues.
More related questions
What happened during the Tymeshift service incident on April 19, 2024?
On April 19, 2024, Tymeshift experienced loading issues across all Pods from 15:24 UTC to 18:34 UTC. During this time, customers may have encountered error messages when trying to load Tymeshift. The issue was due to performance degradation caused…
How was the Tymeshift loading issue resolved on April 19, 2024?
The Tymeshift loading issue on April 19, 2024, was resolved by deploying additional backend resources. This action addressed the performance degradation caused by increased usage, and the service was restored by 18:34 UTC. If you continue to…
What was the root cause of the Tymeshift incident on April 19, 2024?
The root cause of the Tymeshift incident on April 19, 2024, was performance degradation due to increased usage in the specific environment. This led to the app not loading correctly for some customers. The issue was resolved by deploying additional…
When was the Tymeshift service incident fully resolved?
The Tymeshift service incident was fully resolved by 18:34 UTC on April 19, 2024. After deploying additional backend resources, Zendesk confirmed that the access issues were no longer present. Users were encouraged to report any further issues.
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.
