The root cause of the Zendesk email processing incident was connectivity problems with Gmail. The Mail Fetcher service experienced issues where Gmail's 302 Moved responses were misinterpreted as failures by the liveness probe.
This misinterpretation led the container orchestrator to replace the Pods, halting mail processing. The issue was resolved when Gmail stopped blocking health checks, allowing the Pods to be recreated and email processing to resume normally.
On November 16, 2023, Zendesk experienced a service incident affecting inbound email processing. From 18:02 UTC to 20:00 UTC, some customers in Pods 13, 17, 19, 23, 28, and 29 faced delays or stoppages in receiving inbound emails. The issue was due…
The email processing issue on November 16, 2023, affected Zendesk Pods 13, 17, 19, 23, 28, and 29. Customers using these Pods experienced delays or a complete stoppage in receiving inbound emails. The incident was caused by connectivity issues…
The Zendesk email processing issue was resolved by restoring inbound mail traffic after Gmail stopped blocking health checks. This allowed the Support system to recreate its Pods and resume normal email processing. Once the health checks were no…
To prevent future email processing issues, Zendesk is implementing several remediation items. These include improving existing tools for email health checks, creating additional alerts, and adding correction code lines to specific applications….
For more information about Zendesk's current system status, you can check their system status page. This page provides updates on any ongoing issues and the status of Zendesk services. Additionally, summaries of post-mortem investigations are…