Zendesk Support had two separate outages on 29 October 2026, one running 7 hours 44 minutes and a second, shorter one later the same day. Both were on Zendesk's side of the connection, not yours.
Started
00:10 UTC
Duration
Lasted 7h 44m
Source
IsDown
Next time
Zendesk is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Support
What happened?
The first incident started at 00:10 UTC and ran for 7 hours 44 minutes. Zendesk's own title for it was "Some customers are encountering CF error messages accessing Zendesk Support", which points to a Cloudflare-layer problem sitting in front of the Support product rather than the application itself. Zendesk filed no updates at all against this incident, so there is no note on what caused the CF errors, how many accounts were affected, or when a fix actually went in beyond the closing timestamp. A second incident began at 17:45 UTC the same day and lasted 38 minutes, described as "Multiple Products access issues in Pod26", meaning it was scoped to one specific pod rather than Zendesk-wide. That incident also carries zero updates. Only one component is listed as affected across both incidents: Support. No user reports were filed in the window on either incident, so there is no first-hand account of what the errors looked like on screen. Over the past 90 days Zendesk has logged 12 incidents with a median duration of 1 hour 38 minutes, so the 7h 44m first incident is well outside the usual pattern for this provider. Across all time Zendesk averages 7.8 incidents a month, which puts two in one day on the high side but not unprecedented. No post-mortem has been published for either incident.
Learning
UptimeRobot's own 30-day monitoring of Zendesk recorded 4 incidents in that window, all resolved, with a median duration of 4h 12m, numbers that sit closer to what actually happened on 29 October than Zendesk's own terse status entries do. A Cloudflare-layer error in front of Support, or a pod-scoped access problem, can both fail without your own uptime checks against your Zendesk-powered help centre ever going red, because your checks are testing your integration and your domain, not Zendesk's infrastructure sitting behind it. That is the general shape of this kind of failure: the provider's edge or a single pod breaks, your product-side monitoring stays green because it never touches that layer, and support tickets or Cloudflare error pages are the first anyone on your team hears about it. With zero updates published on either incident, you cannot even cross-check Zendesk's own timeline against what your customers were seeing, so external monitoring of the provider itself becomes the only record of how long the disruption actually lasted. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.