Zendesk Service Incident March 6, 2024 Explained
What happened during the Zendesk service incident on March 6, 2024?
On March 6, 2024, Zendesk experienced a service incident affecting Explore users. From 13:33 UTC to 14:15 UTC, customers encountered 502 bad gateway errors when trying to load Explore.
The issue was caused by a process initiated to update the system in the background, which led to temporary 'locking' issues with the database. This resulted in errors for users trying to access Explore. The problem was resolved by 14:07 UTC after clearing stalled queries and restarting the Rails application. For more details, you can check theoriginal link.
More related questions
How was the March 6, 2024, Zendesk incident resolved?
The March 6, 2024, Zendesk incident was resolved by clearing stalled queries and restarting the Rails application. This restored normal operations for Explore. The issue stemmed from a new process introduced to update the system, which caused…
What caused the Zendesk Explore access issues on March 6, 2024?
The access issues with Zendesk Explore on March 6, 2024, were caused by a process initiated to update the system. This process led to temporary 'locking' issues in the database. The Engineering team was working on a new feature to provide usage…
Which Zendesk Explore Pods were affected on March 6, 2024?
On March 6, 2024, the Zendesk Explore access issues specifically affected Pods 17, 18, 28, and 29. Customers using these Pods experienced 502 bad gateway errors when trying to load Explore. The issue was resolved by 14:07 UTC after the necessary…
What steps were taken to prevent future Zendesk Explore incidents?
To prevent future incidents like the one on March 6, 2024, Zendesk planned several remediation steps. These included reviewing and updating the backfill process and processing dashboard_views records asynchronously. These measures aim to ensure…
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.
