Is Zendesk Down?

No — Zendesk is up

Zendesk's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 236 ms

Right now

We could not read Zendesk's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

zendesk.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 236 ms
Checked: 5 hours ago

By region

Amsterdam reachable, 228 ms
Dallas reachable, 140 ms
Frankfurt reachable, 235 ms
Newark reachable, 145 ms
Paris reachable, 245 ms
Stockholm reachable, 124 ms
São Paulo reachable, 445 ms
Toronto reachable, 333 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	24 ms	4 ms	18 ms	206 ms
Dallas	92 ms	2 ms	8 ms	121 ms
Frankfurt	79 ms	2 ms	9 ms	222 ms
Newark	101 ms	2 ms	9 ms	130 ms
Paris	122 ms	1 ms	11 ms	235 ms
Stockholm	80 ms	2 ms	7 ms	105 ms
São Paulo	10 ms	2 ms	10 ms	431 ms
Toronto	277 ms	1 ms	5 ms	318 ms

We check that zendesk.com loads, not every feature behind it. Test it yourself

History

Zendesk website availability

Measured by FlareWarden · zendesk.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 205ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of zendesk.com from multiple regions every 6 hours. Zendesk's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Zendesk itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Zendesk goes down

We check Zendesk every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required