Skip to content

Outage tracker / Zendesk

Is Zendesk down?

I'm having a problem

Partially degradedchecked 15 minutes ago

Zendesk is answering our probes, but its API is running at least 3.3x its 7-day median from South America. Everything else we check answered at its usual speed.

As of Oct 23, 2026, 3:41 AM UTC, RealUptime's checks of Zendesk passed in all 10 regions that returned a reading.

Zendesk's last published incident: "Support Search errors pod 27", Oct 22, 2026, 2h 3m. their claim, not our reading

Front-door and live API checks

Our checks of Zendesk did not fail from two or more distant regions in the 64 days we have checked it (since Aug 20, 2026). This does not show Zendesk works for users.

our check readinglive · checked Oct 23, 2026, 3:41 AM UTC
US-East556 msChecks passing
US-West950 msChecks passing
Europe215 msChecks passing
Asia-Pacific748 msChecks passing
US-Central241 msChecks passing
Canada490 msChecks passing
UK826 msChecks passing
Southeast Asia1363 msChecks passing
Australia871 msChecks passing
South America1898 msDegraded
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 published 2 incidents in the last 30 days. In the same period our checks failed from two or more distant regions 0 times.

Zendesk response time, by region

US-East
498msp95 · 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-09-24 UTC: p95 751ms2026-09-25 UTC: p95 504ms2026-09-26 UTC: p95 545ms2026-09-27 UTC: p95 582ms2026-09-28 UTC: p95 562ms2026-09-29 UTC: p95 570ms2026-09-30 UTC: p95 640ms2026-10-01 UTC: p95 612ms2026-10-02 UTC: p95 576ms2026-10-03 UTC: p95 665ms2026-10-04 UTC: p95 491ms2026-10-05 UTC: p95 577ms2026-10-06 UTC: p95 487ms2026-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 498ms
Sep 24Oct 8Oct 23
US-West
1.1sp95 · 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-09-24 UTC: p95 580ms2026-09-25 UTC: p95 643ms2026-09-26 UTC: p95 639ms2026-09-27 UTC: p95 636ms2026-09-28 UTC: p95 694ms2026-09-29 UTC: p95 642ms2026-09-30 UTC: p95 686ms2026-10-01 UTC: p95 671ms2026-10-02 UTC: p95 575ms2026-10-03 UTC: p95 558ms2026-10-04 UTC: p95 574ms2026-10-05 UTC: p95 664ms2026-10-06 UTC: p95 652ms2026-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 1.1s
Sep 24Oct 8Oct 23
Europe
350msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 546ms2026-09-25 UTC: p95 624ms2026-09-26 UTC: p95 562ms2026-09-27 UTC: p95 491ms2026-09-28 UTC: p95 564ms2026-09-29 UTC: p95 500ms2026-09-30 UTC: p95 429ms2026-10-01 UTC: p95 571ms2026-10-02 UTC: p95 746ms2026-10-03 UTC: p95 665ms2026-10-04 UTC: p95 618ms2026-10-05 UTC: p95 573ms2026-10-06 UTC: p95 609ms2026-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 350ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.0sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 919ms2026-09-25 UTC: p95 993ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 919ms2026-09-29 UTC: p95 922ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 946ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 982ms2026-10-06 UTC: p95 917ms2026-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.0s
Sep 24Oct 8Oct 23
US-Central
255msp95 · 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-09-24 UTC: p95 581ms2026-09-25 UTC: p95 537ms2026-09-26 UTC: p95 550ms2026-09-27 UTC: p95 434ms2026-09-28 UTC: p95 514ms2026-09-29 UTC: p95 707ms2026-09-30 UTC: p95 540ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 406ms2026-10-03 UTC: p95 466ms2026-10-04 UTC: p95 498ms2026-10-05 UTC: p95 466ms2026-10-06 UTC: p95 399ms2026-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 255ms
Sep 24Oct 8Oct 23
Canada
487msp95 · 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-09-24 UTC: p95 835ms2026-09-25 UTC: p95 667ms2026-09-26 UTC: p95 697ms2026-09-27 UTC: p95 543ms2026-09-28 UTC: p95 486ms2026-09-29 UTC: p95 701ms2026-09-30 UTC: p95 599ms2026-10-01 UTC: p95 851ms2026-10-02 UTC: p95 811ms2026-10-03 UTC: p95 782ms2026-10-04 UTC: p95 745ms2026-10-05 UTC: p95 745ms2026-10-06 UTC: p95 658ms2026-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 487ms
Sep 24Oct 8Oct 23
UK
820msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 356ms2026-09-25 UTC: p95 484ms2026-09-26 UTC: p95 580ms2026-09-27 UTC: p95 591ms2026-09-28 UTC: p95 574ms2026-09-29 UTC: p95 483ms2026-09-30 UTC: p95 525ms2026-10-01 UTC: p95 584ms2026-10-02 UTC: p95 508ms2026-10-03 UTC: p95 512ms2026-10-04 UTC: p95 558ms2026-10-05 UTC: p95 408ms2026-10-06 UTC: p95 560ms2026-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 820ms
Sep 24Oct 8Oct 23
Southeast Asia
2.5sp95 · 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-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.4s2026-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.5s
Sep 24Oct 8Oct 23
Australia
834msp95 · 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-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-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 834ms
Sep 24Oct 8Oct 23
South America
1.9sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 788ms2026-09-25 UTC: p95 829ms2026-09-26 UTC: p95 845ms2026-09-27 UTC: p95 936ms2026-09-28 UTC: p95 766ms2026-09-29 UTC: p95 768ms2026-09-30 UTC: p95 932ms2026-10-01 UTC: p95 890ms2026-10-02 UTC: p95 935ms2026-10-03 UTC: p95 992ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 914ms2026-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 1.9s
Sep 24Oct 8Oct 23
Why some readings show as awaiting data. 10 of 20 readings for Zendesk came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Zendesk's health, so we publish no verdict for those readings rather than guessing in either direction. 10 of those readings received an actual response: the connection, the TLS handshake, and the edge all answered, with a measured latency. Our check passed there, just not through the specific path automated checks are filtered on. Read how we tell the difference.

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: Awaiting dataUS-Central: Awaiting dataCanada: Awaiting dataUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Awaiting dataSouth America: Awaiting data
  • 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: Degraded Answering, but 3.3x slower than its 7-day median.

Get an email when our checks of Zendesk fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Zendesk fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Zendesk's official status.

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: 556msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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: 950msstatus code: 200checked: Oct 23, 2026, 3:40 AM 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: 241msstatus code: 200checked: Oct 23, 2026, 3:40 AM 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: 490msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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
    Degradedlatency: 1898msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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: 215msstatus code: 200checked: Oct 23, 2026, 3:41 AM 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: 826msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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: 748msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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: 1363msstatus code: 200checked: Oct 23, 2026, 3:41 AM 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: 871msstatus code: 200checked: Oct 23, 2026, 3:39 AM 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

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
Voice issues pod 20, 3h 57mdeclared on their status page2026-09-17
Ticket Status Deactivated and Unable to Be Reactivated - Multiple Pods, 3h 20mdeclared on their status page2026-09-16
Issues with Voice calls and call functions, 2h 12mdeclared on their status page2026-09-01
Third-Party Apps Experiencing Errors and Timeouts, 1h 42mdeclared on their status page2026-08-19
Pod 28 & 29 Errors - Multiple Products, 1h 24mdeclared on their status page2026-08-13

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

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>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Zendesk's stated SLA

At or above your target

Our checks of Zendesk failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Zendesk's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

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.