Zendesk Outage History

Zendesk is up right now

Pingoru has recorded 49 incidents for Zendesk: 49 in the last 12 months and 12 in the last 90 days.

Source: status.zendesk.com

49incidents recorded
49last 12 months
12last 90 days
21 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct20%
Pingoru began tracking Zendesk in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026530 of 720 (4%)
May 20269138 of 744 (19%)
June 20267142 of 720 (20%)
July 20267228 of 744 (31%)
August 20264133 of 744 (18%)
September 2026416 of 720 (2%)
October 20263114 of 582 (20%)

Incidents, newest first

Major October 23, 2026 US-East degraded traffic 1h 7m Ticketing, Support

Started Oct 23, 2026, 03:20 PM UTC· resolved Oct 23, 2026, 04:27 PM UTC

  1. investigating Oct 23, 2026, 04:09 PM UTC

    Our CDN provider experienced a spike in errors affecting traffic for some customers in US-East between 15:20 and 15:45 UTC, but have significantly improved since that time. We are monitoring the situation to ensure stability; however, some users in that area may still experience degraded traffic and some latency may be expected until they have fully recovered.

  2. resolved Oct 23, 2026, 04:53 PM UTC

    Our CDN provider has released a fix and we are seeing recovery in traffic to affected US-East users. Thank you for your patience as we worked to mitigate the impact and restore access.

Read the full incident report →

Major October 22, 2026 Support Search errors pod 27 2h 3m Search, Support

Started Oct 22, 2026, 02:07 PM UTC· resolved Oct 22, 2026, 04:10 PM UTC

  1. identified Oct 22, 2026, 04:36 PM UTC

    We are beginning to see some improvement in the Search issues affecting Pod 27. Please refresh your browser and let us know if you continue to experience any issues.

  2. resolved Oct 22, 2026, 05:06 PM UTC

    We are happy to report that we have recovered from the issue affecting Search functions within Support on Pod 27, and the issue is now resolved. Thank you for your patience during our investigation.

Read the full incident report →

Minor October 16, 2026 EU customers may experience missing or delayed customer messages in conversation views and analytics data 4d 14h Core Services, AI Agents, Dashboard, Analytics

Started Oct 16, 2026, 06:00 PM UTC· resolved Oct 21, 2026, 08:56 AM UTC

  1. identified Oct 19, 2026, 08:29 AM UTC

    We are aware that customers with AI Agents Advanced data hosted in the EU region may see missing or delayed agent and customer messages in conversation views, as well as missing or delayed analytics data. We understand that incomplete conversation history and reporting can disrupt your work, and we apologize for the impact. Our engineers have applied changes to restore processing and are monitoring recovery while the remaining backlog clears. Based on the current processing rate, we estimate the backlog will clear over the next few hours, with delayed data populating as it is processed. This estimate may change, and some remaining data gaps may require additional recovery work. We continue to investigate these gaps and will provide further updates as recovery progresses. Thank you for your patience while we work to restore complete visibility into your data.

  2. identified Oct 19, 2026, 10:59 AM UTC

    Our engineering teams have completed processing the majority of the backlog that caused agent and customer messages to be delayed or missing from conversation views. The remaining messages are still being processed, and work is also ongoing to restore the related analytics data. We are actively monitoring service performance and recovery progress to ensure that the remaining backlog is processed successfully. Please verify whether the messages that were previously missing are now visible in your conversation views. If any messages remain unavailable or delayed, please contact us with the affected conversation details and approximate message times so that we can investigate further.

  3. identified Oct 19, 2026, 05:13 PM UTC

    Our continued work to backfill missed agent and customer messages in conversation views has uncovered another subset of messages to process. We are monitoring the backfill procedure and our initial estimates show it will be completed tomorrow, Tuesday October 20th. We will provide an update when we can narrow the timeline or if we need to amend the completion target date.

  4. identified Oct 20, 2026, 08:49 AM UTC

    Most previously delayed conversation messages have been processed, but some historical messages remain missing and recovery is not yet complete. We paused the historical message recovery process after it caused delays in another part of the service. Those additional delays have now cleared, and our engineers are developing a revised approach to resume recovery while protecting service stability. We currently do not have a revised completion time; however, we will share further update once the revised recovery plan and timeline are confirmed. We apologize for the continued disruption.

  5. identified Oct 20, 2026, 06:28 PM UTC

    We have another update on the recovery of missing or delayed AI Agent conversation messages. We are monitoring the backlog recovery process and anticipate the new completion date to be October 21st, 2026. Thank you for your understanding and patience. We'll be certain to update when the backlog processing is complete or any new information here.

  6. resolved Oct 21, 2026, 08:22 AM UTC

    We have completed recovery of the historical agent and customer messages affected by this incident for AI Agents Advanced customers hosted in the EU region. Previously missing messages should now be visible in conversation views. We apologize for the disruption and thank you for your patience throughout the recovery.

Read the full incident report →

Major September 21, 2026 Outbound email delivery failures to some mail providers 6h 40m Email, Support

Started Sep 21, 2026, 07:50 AM UTC· resolved Sep 21, 2026, 02:30 PM UTC

  1. resolved Sep 21, 2026, 02:09 PM UTC

    We are aware of an issue impacting outbound email delivery to some mail providers. Some outbound email may fail with an error code 554 -- permanent rejection, meaning the outbound email was not sent and will not be retried. We are working with these mail providers and will provide an update as soon as possible.

  2. resolved Sep 21, 2026, 02:50 PM UTC

    We have observed recovery and are now seeing successful outbound email delivery to the affected email providers. Please let us know if you continue to see any 554 status coded rejections to these recipients. Unfortunately we are unable to resend these emails on your behalf, and we apologize for that inconvenience.

Read the full incident report →

Minor September 17, 2026 Voice issues pod 20 3h 57m Outbound Calls, Voice, Call Recordings / Transcriptions

Started Sep 17, 2026, 02:29 PM UTC· resolved Sep 17, 2026, 06:26 PM UTC

  1. resolved Sep 17, 2026, 04:53 PM UTC

    We are aware of an issue affecting Voice on Pod 20 that is causing agents to experience difficulties leaving wrap-up mode. We are also seeing some call recordings not append to tickets as expected. We are investigating and will provide further information when we have a substantive update to share. In the meantime, we recommend trying to manually click "finish wrap-up" (don't wait for the auto-timeout), and in case "finish wrap-up" doesn't respond, toggle Voice availability Off then On.

  2. resolved Sep 17, 2026, 06:25 PM UTC

    Our team have addressed the underlying cause of the issue that prevented some agents from exiting wrap-up mode after a Voice call. Agents ending a call should see wrap-up, and all relevant agent availability functions are back to normal. Thank you for your patience while we recovered from this incident.

Read the full incident report →

Major September 16, 2026 Ticket Status Deactivated and Unable to Be Reactivated - Multiple Pods 3h 20m Ticketing, Support

Started Sep 16, 2026, 09:00 AM UTC· resolved Sep 16, 2026, 12:20 PM UTC

  1. resolved Sep 16, 2026, 11:14 AM UTC

    We are aware of an issue affecting custom ticket statuses. Some customers may see statuses marked as inactive and be unable to restore them, while other statuses may not appear at all. Our engineering team has identified the cause and is actively working to resolve the issue. We apologize for the disruption and will provide another update as soon as more information is available.

  2. resolved Sep 16, 2026, 11:32 AM UTC

    We have deployed a fix for the issue affecting custom ticket statuses. Please check whether your statuses are now visible and can be managed as expected. If you still see missing or inactive statuses, please reply to let us know. We will be happy to continue investigating with you. We apologize for the disruption and appreciate your help in confirming the resolution.

  3. resolved Sep 16, 2026, 12:13 PM UTC

    Our engineering team is continuing to roll out the fix for the custom ticket status issue to the remaining affected service environments. We appreciate your patience while this work is completed and will provide further updates as they become available.

  4. resolved Sep 16, 2026, 12:41 PM UTC

    Our engineering teams have completed deployment of the fix. Please verify whether custom ticket statuses are now displaying and functioning as expected. If the issue persists, please clear your browser cache and cookies, then check the ticket statuses again using a private or incognito browser window. If the issue continues after these steps, please contact us so we can provide further assistance.

Read the full incident report →

Critical September 1, 2026 Issues with Voice calls and call functions 2h 12m Outbound Calls, Voice, Sales, Inbound Calls and 6 more

Started Sep 01, 2026, 04:15 PM UTC· resolved Sep 01, 2026, 06:27 PM UTC

  1. resolved Sep 01, 2026, 05:23 PM UTC

    We are aware of an issue in the Voice product impacting inbound calls, outbound calls as well as call functions such as putting a call on hold. We will provide updates as soon as they are available.

  2. resolved Sep 01, 2026, 05:35 PM UTC

    Our teams are currently working with our telephony provider to restore all functionality within the Voice product. We will continue to provide updates with any new information. Thank you for your patience.

  3. resolved Sep 01, 2026, 05:56 PM UTC

    We have increased the scope of this incident to include the impact to the Sales product with similar Voice product behavior Calls and Call functions may be impacted. Our telephony provider have now indicated to us that they are now monitoring recovery, and we see similar recovery in our own observability tools. We will provide an update when we are confident the issue is fully resolved.

  4. resolved Sep 01, 2026, 06:26 PM UTC

    Our telephony provider has confirmed full recovery and both the Sales Voice features and Voice product should be fully operational once again. We do apologize for the interruption.

Read the full incident report →

Major August 19, 2026 Third-Party Apps Experiencing Errors and Timeouts 1h 42m Apps, Support, Apps Marketplace

Started Aug 19, 2026, 06:27 AM UTC· resolved Aug 19, 2026, 08:09 AM UTC

  1. resolved Aug 19, 2026, 08:00 AM UTC

    We’re investigating an issue affecting third-party app functionality, where some customers may be unable to use certain apps or may encounter errors and timeouts. Our teams have observed that service is now operating normally. Please refresh your browser and check whether the issue has been resolved on your end.Thank you for your patience as we worked through this.

  2. resolved Aug 19, 2026, 08:33 AM UTC

    We’re happy to report that the issue affecting third-party app functionality has been fully resolved and service has been restored. We appreciate your understanding and cooperation throughout this incident.

Read the full incident report →

Major August 13, 2026 Pod 28 & 29 Errors - Multiple Products 1h 24m Search, Ticketing, Views, Email and 48 more

Started Aug 13, 2026, 03:14 PM UTC· resolved Aug 13, 2026, 04:38 PM UTC

  1. resolved Aug 13, 2026, 04:07 PM UTC

    We are receiving reports of an issue affecting pods 28 and 29 that is causing impact to multiple products, including Sell and Explore, returning errors. We are investigating and will provide further details shortly.

  2. resolved Aug 13, 2026, 04:21 PM UTC

    We have confirmed an issue affecting multiple products on pods 28 and 29, including Explore, Sales, Sunshine Conversations, and Support/Support SDK. Our team is working to mitigate the impact and we will provide additional information when we have a substantive update to share.

  3. resolved Aug 13, 2026, 04:43 PM UTC

    We are beginning to see recovery from the issue affecting multiple products on pods 28 and 29. We will monitor the situation to ensure full recovery across all products. Please let us know if you continue to experience any issues.

  4. resolved Aug 13, 2026, 05:01 PM UTC

    Thank you for your patience while resolved the issue impacting multiple Zendesk products in pod 28 and 29. We have observed full recovery across all of the impacted products.

Read the full incident report →

Major August 4, 2026 Zendesk Support is unaccessible. 37m Ticketing, Support, API, Agent Experience

Started Aug 04, 2026, 11:34 PM UTC· resolved Aug 05, 2026, 12:11 AM UTC

  1. resolved Aug 05, 2026, 12:13 AM UTC

    We are aware of an issue affecting Pod 26 in Zendesk Support that is preventing impacted customers and internal advocates from accessing the service. Our engineering team is currently investigating, and we will provide an update in 30 minutes. Thank you for your patience and understanding.

  2. resolved Aug 05, 2026, 12:27 AM UTC

    We are happy to inform you that the issue affecting Pod 26 in Zendesk Support, which temporarily prevented impacted customers and internal advocates from accessing the service, has now been resolved. Thank you for your patience and understanding.

Read the full incident report →

Major August 3, 2026 Customers in pod 17 have been unable to access Zendesk Product 22m Support, Agent Experience

Started Aug 03, 2026, 06:25 AM UTC· resolved Aug 03, 2026, 06:47 AM UTC

  1. resolved Aug 03, 2026, 11:50 AM UTC

    We are pleased to confirm that our engineering team has verified recovery of the Zendesk Support platform. Service is now fully restored and operating normally. We will continue to closely monitor the situation and will provide an update if any issues emerge. Thank you for your patience during this incident, and we apologize for the disruption you experienced.

Read the full incident report →

Major July 31, 2026 Small number of accounts lost access to AI Agents (Ultimate) during an Employee Service Suite update 4d 7h Core Services, AI Agents

Started Jul 31, 2026, 01:15 AM UTC· resolved Aug 04, 2026, 09:11 AM UTC

  1. resolved Aug 03, 2026, 06:37 AM UTC

    We are investigating an issue where a small number of accounts lost access to AI Agents (Ultimate) on Friday, July 31st at approximately 1:20 AM UTC due to a provisioning process error during an Employee Service Suite update. The affected product is AI Agents Advanced.We are working to restore the access in of the known affected accounts in priority and are implementing safeguards to prevent this from happening again. We continue to investigate the full scope of impact and will provide further updates as soon as it becomes available.

  2. resolved Aug 03, 2026, 09:12 AM UTC

    We have successfully resolved the issue affecting AI Agents access. All identified accounts have had their access restored. The AI Agents service is now fully operational for all affected customers.

  3. resolved Aug 04, 2026, 09:29 AM UTC

    We’ve identified additional accounts that lost access to AI Agents as part of the provisioning issue reported earlier. Our engineering team has completed work to restore access for these accounts, and all identified affected accounts should now have their AI Agents access restored. We apologize for the disruption and appreciate your patience while we worked to resolve this issue.

Read the full incident report →

Major July 24, 2026 Unable to Access Zendesk 1h 24m Ticketing, Agent Workspace (via Support), API, Core Services and 21 more

Started Jul 24, 2026, 11:18 AM UTC· resolved Jul 24, 2026, 12:42 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major July 23, 2026 Exchange Connector: No Retry on Outbound Emails 15d 3h Email, Support

Started Jul 23, 2026, 10:14 AM UTC· resolved Aug 07, 2026, 01:32 PM UTC

  1. resolved Aug 07, 2026, 10:40 AM UTC

    We're aware of an issue affecting email retries in our Exchange connector. Our engineering team is currently investigating and working on a resolution. We'll provide updates as soon as we have more information.

  2. resolved Aug 07, 2026, 03:06 PM UTC

    We are happy to report that the issue affecting outbound email retries in our Exchange connector has been resolved, and the backfill for affected emails has been initiated. Any missed retried emails during the window of impact should be processed shortly, and appear as expected. Thank you for your patience during our investigation.

Read the full incident report →

Major July 16, 2026 Customers in Pod 25 experiencing Chat Ticket creation delays in Agent Workspace 1h 44m API, Dashboard, Chat

Started Jul 16, 2026, 03:50 AM UTC· resolved Jul 16, 2026, 05:34 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major July 14, 2026 Bot messages looping & repeating 1h 27m AI Agents, Web Chat Widget

Started Jul 14, 2026, 04:45 PM UTC· resolved Jul 14, 2026, 06:13 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major July 9, 2026 Elevated errors loading Solve Widget 32m Forethought AI Agents, Widget

Started Jul 09, 2026, 04:59 PM UTC· resolved Jul 09, 2026, 05:31 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 9, 2026 Attachments failing to load in Side Conversations 4h 39m Email, Agent Workspace (via Support), Support

Started Jul 09, 2026, 12:10 PM UTC· resolved Jul 09, 2026, 04:49 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major June 26, 2026 Issues accessing Zendesk Sales features including Deals 1d 10h Sales, API, Web Interface

Started Jun 26, 2026, 05:37 PM UTC· resolved Jun 28, 2026, 03:45 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 25, 2026 Malformed AI Agent “ask for details” forms via social channels app such as WhatsApp. 5d 22h Third-Party Channels, Support, AI Agents, Sunshine Conversations and 2 more

Started Jun 25, 2026, 02:59 PM UTC· resolved Jul 01, 2026, 01:46 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major June 22, 2026 Support access issues across multiple pods 50m Support, Misc

Started Jun 22, 2026, 01:33 PM UTC· resolved Jun 22, 2026, 02:23 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major June 19, 2026 AI Agents degradation due to Open AI issues 42m Core Services, Support, AI Agents

Started Jun 19, 2026, 02:19 PM UTC· resolved Jun 19, 2026, 03:01 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical June 12, 2026 Issue with Social Messaging Channels 2h 57m Misc, Third-Party Channels, Support, Chat and 1 more

Started Jun 12, 2026, 01:33 PM UTC· resolved Jun 12, 2026, 04:30 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major June 12, 2026 Unable to access Analytics (Explore) 9h 5m Analytics, Dashboard Scheduling & Sharing

Started Jun 12, 2026, 12:40 PM UTC· resolved Jun 12, 2026, 09:46 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major June 11, 2026 AI Agents Advanced Dashboard issues 41m AI Agents, Dashboard

Started Jun 11, 2026, 05:00 PM UTC· resolved Jun 11, 2026, 05:41 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →