Zendesk's Support Search function broke for 39 minutes on 22 October 2026, affecting pod 27. The fault sat on Zendesk's side, logged as "Support Search errors pod 27" on its own status page.
Started
16:35 UTC
Duration
Lasted 39m
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?
Zendesk's status page recorded one incident on 22 October 2026, titled "Support Search errors pod 27", starting at 16:35 UTC and lasting 39 minutes. The affected component was listed simply as Support, with no further breakdown given. Zendesk filed no updates at all during the incident, zero in total, so there is no detail on what search queries failed, which agents were affected, or how the fault was found and fixed. No user reports were filed during this window either, which may mean the impact was narrow, confined to one pod, or simply that nobody filing the UptimeRobot record happened to be on pod 27 at the time. Over the past 90 days Zendesk has logged 11 incidents with a median duration of 1 hour 39 minutes, so this one resolved faster than typical. Across its history, Zendesk has filed 507 incidents at a rate of about 7.8 per month, putting search and pod-specific faults well within its normal pattern. With zero updates published, you are left with the title, the timestamp and the duration, and nothing else on the public record to confirm root cause. Zendesk has not said why Search broke on pod 27, and no post-mortem has been published.
Learning
Zendesk's own status page names the broken piece precisely, pod 27, Support Search, but a status page entry with zero updates tells you almost nothing about scope or cause, only that Zendesk's internal monitoring caught something and closed it within 39 minutes. If your product depends on Zendesk Support search and you were only watching your own endpoints, you would have seen your calls to Zendesk's API either succeed, fail, or time out, depending on whether your traffic happened to land on pod 27. That is the shape of multi-tenant pod failures: they are real, documented outages, and they can be invisible to you entirely if your account sits on an unaffected pod, or total if it doesn't. UptimeRobot's own 30 day data shows 2 incidents against Zendesk with a median resolution time of 24h 44m, a very different number from the 39 minutes Zendesk logged here, because the two are measuring different things from different vantage points. Your own monitoring tells you whether your integration with Zendesk is working right now. UptimeRobot watches Zendesk's own status and uptime pattern so you have a second, independent read on whether a slowdown is your problem or theirs, without waiting on a vendor update that may never come.