Skip to content

Outage tracker / Zendesk

Is Zendesk down?

I'm having a problem

Vendor reports no incidentWhat Zendesk reports

Zendesk reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:10 UTC.

Zendesk's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 5 minutes ago

Our checks of Zendesk pass from all 10 regions we check.

As of Nov 5, 2026, 3:05 PM UTC, RealUptime's checks of Zendesk passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:05 PM UTC
US-East1111 msChecks passing
US-West1466 msChecks passing
Europe1082 msChecks passing
Asia-Pacific1446 msChecks passing
US-Central464 msChecks passing
Canada1214 msChecks passing
UK318 msChecks passing
Southeast Asia424 msChecks passing
Australia520 msChecks passing
South America885 msChecks passing
their status pagetheir claim, not our reading

Zendesk publishes no status feed we can read, so the only reading here is our check reading on the left.

Zendesk response time, by region

US-East
1.2sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 468ms2026-10-08 UTC: p95 493ms2026-10-09 UTC: p95 515ms2026-10-10 UTC: p95 562ms2026-10-11 UTC: p95 549ms2026-10-12 UTC: p95 530ms2026-10-13 UTC: p95 580ms2026-10-14 UTC: p95 354ms2026-10-15 UTC: p95 464ms2026-10-16 UTC: p95 599ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 691ms2026-10-24 UTC: p95 670ms2026-10-25 UTC: p95 633ms2026-10-26 UTC: p95 840ms2026-10-27 UTC: p95 717ms2026-10-28 UTC: p95 769ms2026-10-29 UTC: p95 816ms2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 588ms2026-10-08 UTC: p95 621ms2026-10-09 UTC: p95 581ms2026-10-10 UTC: p95 587ms2026-10-11 UTC: p95 664ms2026-10-12 UTC: p95 502ms2026-10-13 UTC: p95 490ms2026-10-14 UTC: p95 587ms2026-10-15 UTC: p95 679ms2026-10-16 UTC: p95 461ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 420ms2026-10-21 UTC: p95 393ms2026-10-22 UTC: p95 782ms2026-10-23 UTC: p95 982ms2026-10-24 UTC: p95 623ms2026-10-25 UTC: p95 918ms2026-10-26 UTC: p95 821ms2026-10-27 UTC: p95 941ms2026-10-28 UTC: p95 919ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Europe
1.1sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 650ms2026-10-08 UTC: p95 518ms2026-10-09 UTC: p95 526ms2026-10-10 UTC: p95 635ms2026-10-11 UTC: p95 580ms2026-10-12 UTC: p95 561ms2026-10-13 UTC: p95 456ms2026-10-14 UTC: p95 589ms2026-10-15 UTC: p95 529ms2026-10-16 UTC: p95 441ms2026-10-17 UTC: p95 694ms2026-10-18 UTC: p95 657ms2026-10-19 UTC: p95 815ms2026-10-20 UTC: p95 426ms2026-10-21 UTC: p95 438ms2026-10-22 UTC: p95 496ms2026-10-23 UTC: p95 626ms2026-10-24 UTC: p95 536ms2026-10-25 UTC: p95 498ms2026-10-26 UTC: p95 441ms2026-10-27 UTC: p95 616ms2026-10-28 UTC: p95 948ms2026-10-29 UTC: p95 616ms2026-10-30 UTC: p95 836ms2026-10-31 UTC: p95 891ms2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Asia-Pacific
1.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 967ms2026-10-08 UTC: p95 879ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 892ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 916ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 659ms2026-10-21 UTC: p95 522ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-Central
714msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 599ms2026-10-08 UTC: p95 514ms2026-10-09 UTC: p95 405ms2026-10-10 UTC: p95 408ms2026-10-11 UTC: p95 668ms2026-10-12 UTC: p95 455ms2026-10-13 UTC: p95 528ms2026-10-14 UTC: p95 608ms2026-10-15 UTC: p95 323ms2026-10-16 UTC: p95 478ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 306ms2026-10-21 UTC: p95 455ms2026-10-22 UTC: p95 383ms2026-10-23 UTC: p95 427ms2026-10-24 UTC: p95 497ms2026-10-25 UTC: p95 512ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 746ms2026-10-28 UTC: p95 537ms2026-10-29 UTC: p95 346ms2026-10-30 UTC: p95 632ms2026-10-31 UTC: p95 663ms2026-11-01 UTC: p95 601ms2026-11-02 UTC: p95 630ms2026-11-03 UTC: p95 886ms2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 714ms
Oct 7Oct 21Nov 5
Canada
1.4sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 610ms2026-10-08 UTC: p95 584ms2026-10-09 UTC: p95 587ms2026-10-10 UTC: p95 583ms2026-10-11 UTC: p95 721ms2026-10-12 UTC: p95 536ms2026-10-13 UTC: p95 883ms2026-10-14 UTC: p95 658ms2026-10-15 UTC: p95 432ms2026-10-16 UTC: p95 481ms2026-10-17 UTC: p95 601ms2026-10-18 UTC: p95 597ms2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 666ms2026-10-24 UTC: p95 371ms2026-10-25 UTC: p95 374ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 476ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 775ms2026-10-30 UTC: p95 636ms2026-10-31 UTC: p95 587ms2026-11-01 UTC: p95 597ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 813ms2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 458ms2026-10-09 UTC: p95 460ms2026-10-10 UTC: p95 855ms2026-10-11 UTC: p95 655ms2026-10-12 UTC: p95 645ms2026-10-13 UTC: p95 296ms2026-10-14 UTC: p95 413ms2026-10-15 UTC: p95 537ms2026-10-16 UTC: p95 752ms2026-10-17 UTC: p95 585ms2026-10-18 UTC: p95 787ms2026-10-19 UTC: p95 773ms2026-10-20 UTC: p95 454ms2026-10-21 UTC: p95 396ms2026-10-22 UTC: p95 773ms2026-10-23 UTC: p95 820ms2026-10-24 UTC: p95 430ms2026-10-25 UTC: p95 514ms2026-10-26 UTC: p95 397ms2026-10-27 UTC: p95 445ms2026-10-28 UTC: p95 416ms2026-10-29 UTC: p95 769ms2026-10-30 UTC: p95 842ms2026-10-31 UTC: p95 916ms2026-11-01 UTC: p95 983ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
4.0sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 661ms2026-10-25 UTC: p95 670ms2026-10-26 UTC: p95 721ms2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 883ms2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 4.0s
Oct 7Oct 21Nov 5
Australia
1.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 934ms2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 3.5s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 948ms2026-10-24 UTC: p95 902ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 905ms2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 579ms2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
South America
1.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 748ms2026-10-08 UTC: p95 835ms2026-10-09 UTC: p95 661ms2026-10-10 UTC: p95 786ms2026-10-11 UTC: p95 704ms2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 947ms2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 573ms2026-10-21 UTC: p95 760ms2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 7.0s2026-10-24 UTC: p95 873ms2026-10-25 UTC: p95 641ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 800ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5

Check your own site while you wait on Zendesk

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Zendesk. It cannot diagnose Zendesk's own systems.

What we measured, function by function

Zendesk answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Zendesk reports an incident on its status page, and again when it reports it resolved.

Get an email when Zendesk reports an incident

Email me when Zendesk reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Zendesk's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1111msstatus code: 200checked: Nov 5, 2026, 3:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Zendesk normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1466msstatus code: 200checked: Nov 5, 2026, 2:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Zendesk normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 464msstatus code: 200checked: Nov 5, 2026, 2:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Zendesk normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1214msstatus code: 200checked: Nov 5, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Zendesk normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 885msstatus code: 200checked: Nov 5, 2026, 2:13 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Zendesk normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1082msstatus code: 200checked: Nov 5, 2026, 2:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Zendesk normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 318msstatus code: 200checked: Nov 5, 2026, 2:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Zendesk normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1446msstatus code: 200checked: Nov 5, 2026, 2:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Zendesk normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 424msstatus code: 200checked: Nov 5, 2026, 2:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Zendesk normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 520msstatus code: 200checked: Nov 5, 2026, 2:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Zendesk normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Zendesk, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Zendesk yet, which is not evidence that nothing is wrong.

Recent probe events

AI Agents are unresponsive, 5h 10mdeclared on their status page2026-11-03
Multiple Products access issues in Pod26, 30mdeclared on their status page2026-10-29
Forethought Login Issues, 2h 40mdeclared on their status page2026-10-29
Some customers are encountering CF error messages accessing Zendesk Support, 1h 10mdeclared on their status page2026-10-28
US-East degraded traffic, 2h 58mdeclared on their status page2026-10-23
Support Search errors pod 27, 2h 3mdeclared on their status page2026-10-22
EU customers may experience missing or delayed customer messages in conversation views and analytics data, 110h 57mdeclared on their status page2026-10-16
Outbound email delivery failures to some mail providers, 6h 40mdeclared on their status page2026-09-21

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Zendesk since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Zendesk covering any window you pick, with our check readings and Zendesk's own claim at the time, side by side.

Full check history for Zendesk: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Zendesk uptime by RealUptime's checksLive, from this page's own readings.
[![Zendesk uptime by RealUptime's checks](https://realuptime.io/outages/zendesk/badge.svg?days=30)](https://realuptime.io/outages/zendesk)
<a href="https://realuptime.io/outages/zendesk"><img src="https://realuptime.io/outages/zendesk/badge.svg?days=30" alt="Zendesk uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Zendesk down?", https://realuptime.io/outages/zendesk. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://support.zendesk.com/api/v2/users/me.json
secondary
https://status.zendesk.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: support.zendesk.com

RealUptime is not affiliated with Zendesk; the name identifies what we checked, and nothing here speaks for Zendesk's own team. We send a single web request to Zendesk from 10 regions on our own schedule and time the response. We do not see inside Zendesk's systems, do not use an account or real transaction, and are not the same signal Zendesk's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Zendesk is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.