Customer service software for text, mobile, phone, email, chat, social.
There were 98 Zendesk outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Not working for you?
Minor
: Zendesk ticket loading issues affect customers on Pod 29
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
Some Zendesk Support customers on Pod 29 were unable to load tickets or work on affected tickets from to . Zendesk reported that the issue had recovered; its status page later marked Support / Ticketing as fully restored.
Minor
: Zendesk 429 errors disrupt Support and Exchange email delivery
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
Zendesk customers encountered 429 errors and “Access temporarily restricted” notifications, including issues with mail delivery through the Microsoft Exchange Connector. Zendesk began investigating at and attributed the errors to a temporary spike in traffic affecting some customers.
Zendesk reported recovery from the traffic spike at and continued monitoring before marking the incident resolved at . The affected Support components returned to normal, with the disruption lasting about 50 minutes.
Major
: Zendesk email delivery disrupted through Microsoft Exchange Connector
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day, 1 hour and 5 minutes)
Inbound and outbound email delivery through the Zendesk Microsoft Exchange Connector was disrupted starting during an issue Microsoft was working to resolve. Zendesk automatically retried inbound mail and later began resending queued outbound messages as service recovered. Delays could cause ticket comments to appear out of order, and Zendesk continued backfilling outbound mail after email delivery was marked restored at .
During recovery, some customers also encountered 429 errors and “Access temporarily restricted” notifications in Agent Workspace. Zendesk attributed these errors to a temporary traffic spike and reported recovery by , with the component fully resolved at .
Major
: Zendesk AI Agents outage disrupts automated support
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours and 45 minutes)
An outage affected Zendesk's AI Agents, making AI-driven responses unresponsive, and preventing escalation to human agents or loading the AI Agents dashboard. The issue began at and disrupted the AI Agents core services and dashboard for several hours, impacting automated support workflows across multiple customer channels.
Zendesk rolled out recovery steps, including a staged redeployment and service restarts. EU customers saw improvements earlier, with US rollout following to mitigate impact. By , the AI Agents core services and the dashboard had been restored for most users, marking the start of full recovery.
Zendesk experienced brief access issues in Pod26 affecting access to multiple Zendesk products via the Support / API. The outage began at and a rollback of a recent change was implemented to restore access. By the Support / API component had returned to up and Zendesk indicated the service was restored.
A brief login outage prevented access to Zendesk Forethought dashboards for some users. The disruption occurred between and , with agents seeing the error PreAuthentication failed with error There was an error retrieving user information during sign-in. Forethought AI Agents / Dashboard was the affected component, and corrective action was taken by .
Zendesk Support experienced a regional outage in the Mexico region, with customers encountering CF error messages when trying to reach Zendesk Support. The issue began at and affected the Support/API component. A regional recovery was observed as CDN traffic was rerouted, with Mexico traffic returning toward normal by and full restoration achieved by . The outage was localized to Mexico, and Zendesk continued monitoring the situation as services were restored.
Minor
: Zendesk Support regional outage in Mexico; service restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours)
Zendesk Support experienced a regional outage impacting access for users in Mexico. The incident began at with Cloudflare error messages when loading Zendesk Support, and Zendesk’s status updates noted a network connectivity issue in the Mexico region. A CDN partner subsequently identified a regional outage affecting Mexico, with engineers reporting signs of recovery as the situation developed.
Over the next hours, access began to improve, and by the affected Support / API component had recovered, restoring access for most users. The outage was regional in scope, centered on Mexico, and Zendesk continued to monitor the situation and provide updates as fixes were implemented.
Minor
: Zendesk US-East outage disrupts Support / Ticketing
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(45 minutes)
US-East users faced degraded traffic and higher latency as a CDN provider encountered errors, affecting Zendesk traffic between and . The issue progressed to a partial outage for Zendesk's Support / Ticketing component, with the status showing the component down from and remaining unavailable until . Recovery followed as the CDN problems abated, though some users in US-East may have continued to experience degraded traffic and latency until full stabilization.
Zendesk's status page updates described the degradation in US-East linked to the CDN provider and the subsequent restoration of the Support / Ticketing service. The incident underscores how regional backbone issues can impact a core support channel even after broad recovery.
Minor
: Zendesk Support Search outage on Pod 27; brief disruption
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(40 minutes)
Zendesk experienced a brief outage affecting the Support Search function on Pod 27. Users attempting to perform searches in Zendesk Support likely encountered errors or incomplete results. The issue began at and was resolved by , lasting about 40 minutes.
Zendesk's status updates described the incident as Support Search errors on Pod 27, with later communication confirming the issue had been resolved and that the Search feature had returned to normal on Pod 27.