To prevent future incidents similar to the one on November 22, 2023, Zendesk planned several remediation steps. These include updating the Change Management Process to prioritize the impact of asset changes and ensuring that assets are only used by the rightful applications.
Additionally, Zendesk aims to resolve the CDN provider API rate limit issues that contributed to the delay in rolling back the changes. These measures are intended to enhance the stability and reliability of the platform, reducing the likelihood of similar incidents occurring in the future.
On November 22, 2023, Zendesk experienced a service incident where users encountered blank pages when trying to access certain settings in the Admin Center. This issue affected all Pods and lasted from 10:05 UTC to 12:50 UTC. Despite the blank…
The Zendesk service incident on November 22, 2023, was resolved by rolling back a recent change that affected access to the Admin Center. This change had caused blank pages to appear when users tried to access certain settings. The rollback process…
The root cause of the Zendesk service incident on November 22, 2023, was changes to security settings headers for Admin Center translation assets. These changes were intended to improve data handling but inadvertently blocked necessary information,…
The Zendesk service incident on November 22, 2023, lasted for approximately 2 hours and 45 minutes. It began at 10:05 UTC and was resolved by 12:50 UTC. During this time, users experienced issues accessing certain settings in the Admin Center,…