Updates During Zendesk July 2, 2024 Incident
What updates were provided during the Zendesk incident on July 2, 2024?
During the Zendesk incident on July 2, 2024, several updates were provided. Initially, Zendesk acknowledged the issue with the "Accept Chat" button on Pods 17 and 18 and continued to investigate. They explored fixes and tested options to resolve the issue. Later, they increased capacity on Messaging services and monitored for additional impacts. Finally, they confirmed the resolution of the issue after further monitoring.
More related questions
What happened during the Zendesk service incident on July 2, 2024?
On July 2, 2024, Zendesk experienced a service incident affecting Pods 17 and 18, where the "Accept Chat" button became unresponsive. This issue later spread, causing a "Couldn't connect to server" error for customers in multiple other Pods when…
How did Zendesk resolve the July 2, 2024 service incident?
Zendesk resolved the July 2, 2024 service incident by implementing a multi-pronged approach. They increased the size of database clusters across all pods and identified database locks and blocked transactions as the root cause. A fast fix was…
What was the root cause of the Zendesk incident on July 2, 2024?
The root cause of the Zendesk incident on July 2, 2024, was linked to performance challenges during an upgrade to their updated storage system. These challenges resulted in a lag in delivering timely updates due to issues processing queries for…
What remediation steps did Zendesk take after the July 2, 2024 incident?
After the July 2, 2024 incident, Zendesk took several remediation steps. They removed database locks and cleaned up orphaned subscriptions. Additionally, they added Service Level Objectives (SLOs) for connection and subscription creation endpoints…
How long did the Zendesk service incident on July 2, 2024 last?
The Zendesk service incident on July 2, 2024, lasted from 08:10 UTC to 16:30 UTC. During this time, customers across Pods 17 and 18 faced issues with the "Accept Chat" button being unresponsive, and later, a "Couldn't connect to server" error…
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.
