Skip to main content
Zendesk logo

Is Zendesk Down?

No — Zendesk is up

Reachable from all 5 checked regions

Average response time: 39ms

Last checked · checks run every 6 hours

Official status page: https://status.zendesk.com

Zendesk uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
112ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 13 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
44ms
DNS 0ms TCP 1ms TLS 8ms TTFB 30ms
arn
52ms
DNS 1ms TCP 1ms TLS 7ms TTFB 36ms
bom
282ms
DNS 11ms TCP 9ms TLS 12ms TTFB 258ms
ord
42ms
DNS 0ms TCP 2ms TLS 6ms TTFB 27ms
sin
198ms
DNS 0ms TCP 0ms TLS 12ms TTFB 184ms
sjc
26ms
DNS 0ms TCP 0ms TLS 6ms TTFB 19ms
syd
43ms
DNS 0ms TCP 1ms TLS 6ms TTFB 33ms
yyz
40ms
DNS 0ms TCP 5ms TLS 10ms TTFB 30ms

What Zendesk does

Zendesk is a customer service platform combining ticketing, messaging and live chat, voice and a knowledge base. Support teams run their whole queue through it, and companies embed its widget inside their own products, so an outage stops a business answering its customers rather than merely inconveniencing the people who work there.

What an outage looks like

Agents cannot load the ticket queue, or tickets fail to save when submitted. The embedded widget and help centre stop rendering for customers, so inbound requests never arrive in the first place. Live chat sessions disconnect mid-conversation. Calls placed through Zendesk voice fail to connect or drop, and reporting views load stale or empty.

What to do about it

Check status.zendesk.com for which parts of the suite are affected, since ticketing, messaging, voice and the knowledge base fail independently of each other. Put a notice on another channel your customers already use: a widget that will not render gives them no signal that their message failed. Avoid resubmitting tickets in bulk, because duplicates surface once the queue recovers.

Is it down for everyone, or just you?

If this page says Zendesk is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Intercom
Intercom
Salesforce
Salesforce
HubSpot
HubSpot
Slack
Slack

Zendesk outage FAQ

Is Zendesk down or is my help centre misconfigured?
Ask whether agents can load the ticket queue. If the internal agent interface works and only the customer-facing widget or help centre fails, the problem is more likely your own configuration, theme or a content security policy blocking the script. A genuine outage affects both sides at once, and status.zendesk.com reports the suite by component.
Are customer tickets lost during a Zendesk outage?
Tickets that reached Zendesk are stored and appear once the queue recovers. The real gap is on the customer side: if the widget never rendered, no request was ever created, and there is no record of the attempt. That silent failure is why publishing a fallback contact route matters more than worrying about stored data.
Does a Zendesk outage affect email support as well as chat?
They can fail independently. Messaging and live chat run separately from the ticketing pipeline that turns inbound email into tickets, so chat can drop while email-created tickets keep arriving, or the reverse. Check which components the status page names before telling customers which channel to use instead of the one that is broken.
Why can agents see old tickets but not create new ones?
Reads and writes fail separately in most incidents. Serving an already-stored ticket is cheaper than accepting a new one, which touches the queue, triggers automations and notifies people. A partially degraded Zendesk commonly shows exactly this: history loads, submissions error. Avoid retrying a submission repeatedly, since some attempts land despite returning an error.
What should support teams do while Zendesk is unavailable?
Move to a channel that still works, usually a shared mailbox or a social account, and say so where customers will see it. Log what you handle off-platform so it can be reconciled afterwards. When the queue returns, expect a backlog arriving at once and agree who takes it before everyone replies to the same tickets.

How we measure this

  • We request Zendesk's public endpoint every 6 hours from Fly.io regions across six continents — 5 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Zendesk publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Zendesk goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required