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 technical adjustments were made to clear the database locks.
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…
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…
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…
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…