# Zendesk status > Is Zendesk down? Live status, uptime history, and per-region response times measured by our own probes every 2 minutes. Published: 2026-09-07 | Canonical: https://yoping.me/status/zendesk ## How we check Zendesk We watch zendesk.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses. Every Zendesk customer runs on their own subdomain, so no single URL represents every account the way a shared login host would. We watch Zendesk's own site and pin the specific response an anonymous request receives, rather than assuming a 2xx, as the closest thing to a shared signal a platform of independent subdomains has. The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/zendesk. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page. ## What is Zendesk? Zendesk runs customer support software across a large number of independent customer instances, each on its own subdomain and often its own custom domain layered on top, while the underlying ticketing, routing, and automation infrastructure is shared across all of them. That architecture means "is Zendesk down" is rarely a single answer across every customer, which is worth knowing before treating your account being unreachable as proof of a platform-wide incident. Instances are distributed across multiple infrastructure pods, and an incident is frequently scoped to one pod rather than the whole platform. Two support teams can have completely different experiences during the same announced Zendesk event, and neither report is wrong, because which pod hosts your instance decides whether an incident actually touches you. Zendesk's own status page breaks incidents down at that level, which is more useful during a real event than any single outside reading. Custom domains add a specific failure mode worth knowing about separately from Zendesk's own health. A vanity URL pointed at your Zendesk instance depends on its own DNS configuration and, if serving over HTTPS, its own certificate, both of which can lapse or misconfigure independently of Zendesk's infrastructure. An expired certificate on a custom domain produces an unreachable helpdesk that looks exactly like a platform outage and has nothing to do with one. Marketplace apps are the other frequent source of trouble that gets attributed to Zendesk itself. An app installed to extend the helpdesk, particularly one that hooks into ticket creation or routing, can break in a way that makes part of the support workflow appear broken while Zendesk's core platform answers every request correctly. Disabling recently installed or updated apps is often a faster diagnosis than waiting on a status update. Rate limiting is the most common source of API errors for teams building integrations on top of Zendesk. Every plan enforces limits on API calls, and exceeding one produces an error from a service that remains completely healthy, resolved by spacing out requests or requesting a higher limit rather than by anything on Zendesk's side needing to recover. ## Frequently asked questions ### Is Zendesk down right now? Check the board above; it reflects our own probes against Zendesk's own site from all five of our regions, refreshed every couple of minutes. Your organisation's helpdesk runs on its own subdomain, so this is a reading of Zendesk's shared infrastructure rather than a check of your specific instance. ### Our helpdesk subdomain is unreachable but this page shows Zendesk up. What should I check? Check Zendesk's status page for incidents scoped to your specific pod or region, because Zendesk runs customer instances across multiple infrastructure pods and an incident is often scoped to one of them rather than the whole platform. A recently changed custom domain, an expired SSL certificate on a vanity URL, or an app installed from the marketplace can also make one instance unreachable while Zendesk broadly reports healthy. ### Does a Zendesk outage lose tickets that were already submitted? No. An outage affects the ability to reach and update tickets going forward, not the durability of tickets already recorded. The practical question after any incident is whether a ticket submitted through email or an integration during the window arrived and simply was not visible yet, which the audit log settles more reliably than assuming either outcome. ### Is the Zendesk status page the same as this one? No. Zendesk's own status page reports what their team has confirmed internally, broken down by pod and component, in more detail than an outside probe can offer. This page reports what our own probes measured from outside Zendesk's infrastructure, on a fixed schedule, whether or not Zendesk has posted an update yet. ### An integration using the Zendesk API is failing with rate-limit errors. Is that an outage? No, a rate-limit response means the API answered and is enforcing a limit tied to your plan and endpoint. Spacing out requests, batching where the API supports it, or requesting a higher limit through Zendesk resolves it, and none of it reflects a platform incident.