Skip to content

Outage tracker / Zendesk

Is Zendesk down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Zendesk from all 10 regions we check.

As of Oct 5, 2026, 8:17 PM UTC, Zendesk answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Zendesk (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:17 PM UTC
US-East591 msOperational
US-West445 msOperational
Europe335 msOperational
Asia-Pacific1000 msOperational
US-Central499 msOperational
Canada475 msOperational
UK341 msOperational
Southeast Asia1191 msOperational
Australia756 msOperational
South America682 msOperational
their status pagetheir claim, not our reading

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

Zendesk response time, by region

US-East
571msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 516ms2026-09-07 UTC: p95 483ms2026-09-08 UTC: p95 441ms2026-09-09 UTC: p95 351ms2026-09-10 UTC: p95 466ms2026-09-11 UTC: p95 477ms2026-09-12 UTC: p95 478ms2026-09-13 UTC: p95 483ms2026-09-14 UTC: p95 532ms2026-09-15 UTC: p95 509ms2026-09-16 UTC: p95 700ms2026-09-17 UTC: p95 660ms2026-09-18 UTC: p95 741ms2026-09-19 UTC: p95 676ms2026-09-20 UTC: p95 636ms2026-09-21 UTC: p95 490ms2026-09-22 UTC: p95 504ms2026-09-23 UTC: p95 585ms2026-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 571ms
Sep 6Sep 20Oct 5
US-West
635msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 767ms2026-09-07 UTC: p95 761ms2026-09-08 UTC: p95 647ms2026-09-09 UTC: p95 392ms2026-09-10 UTC: p95 343ms2026-09-11 UTC: p95 429ms2026-09-12 UTC: p95 488ms2026-09-13 UTC: p95 478ms2026-09-14 UTC: p95 486ms2026-09-15 UTC: p95 670ms2026-09-16 UTC: p95 807ms2026-09-17 UTC: p95 830ms2026-09-18 UTC: p95 873ms2026-09-19 UTC: p95 878ms2026-09-20 UTC: p95 782ms2026-09-21 UTC: p95 800ms2026-09-22 UTC: p95 725ms2026-09-23 UTC: p95 613ms2026-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 635ms
Sep 6Sep 20Oct 5
Europe
503msp95 · 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-06 UTC: p95 433ms2026-09-07 UTC: p95 415ms2026-09-08 UTC: p95 447ms2026-09-09 UTC: p95 529ms2026-09-10 UTC: p95 501ms2026-09-11 UTC: p95 507ms2026-09-12 UTC: p95 528ms2026-09-13 UTC: p95 485ms2026-09-14 UTC: p95 414ms2026-09-15 UTC: p95 462ms2026-09-16 UTC: p95 547ms2026-09-17 UTC: p95 550ms2026-09-18 UTC: p95 537ms2026-09-19 UTC: p95 478ms2026-09-20 UTC: p95 541ms2026-09-21 UTC: p95 561ms2026-09-22 UTC: p95 562ms2026-09-23 UTC: p95 474ms2026-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 503ms
Sep 6Sep 20Oct 5
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-06 UTC: p95 879ms2026-09-07 UTC: p95 927ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 961ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 916ms2026-09-13 UTC: p95 835ms2026-09-14 UTC: p95 870ms2026-09-15 UTC: p95 960ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.4s2026-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 1.0s
Sep 6Sep 20Oct 5
US-Central
404msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 523ms2026-09-07 UTC: p95 651ms2026-09-08 UTC: p95 690ms2026-09-09 UTC: p95 639ms2026-09-10 UTC: p95 590ms2026-09-11 UTC: p95 685ms2026-09-12 UTC: p95 642ms2026-09-13 UTC: p95 505ms2026-09-14 UTC: p95 603ms2026-09-15 UTC: p95 546ms2026-09-16 UTC: p95 668ms2026-09-17 UTC: p95 635ms2026-09-18 UTC: p95 414ms2026-09-19 UTC: p95 501ms2026-09-20 UTC: p95 467ms2026-09-21 UTC: p95 503ms2026-09-22 UTC: p95 475ms2026-09-23 UTC: p95 495ms2026-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 404ms
Sep 6Sep 20Oct 5
Canada
747msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 592ms2026-09-07 UTC: p95 626ms2026-09-08 UTC: p95 692ms2026-09-09 UTC: p95 712ms2026-09-10 UTC: p95 644ms2026-09-11 UTC: p95 697ms2026-09-12 UTC: p95 636ms2026-09-13 UTC: p95 762ms2026-09-14 UTC: p95 676ms2026-09-15 UTC: p95 677ms2026-09-16 UTC: p95 763ms2026-09-17 UTC: p95 723ms2026-09-18 UTC: p95 673ms2026-09-19 UTC: p95 648ms2026-09-20 UTC: p95 594ms2026-09-21 UTC: p95 565ms2026-09-22 UTC: p95 545ms2026-09-23 UTC: p95 807ms2026-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 747ms
Sep 6Sep 20Oct 5
UK
380msp95 · 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-06 UTC: p95 474ms2026-09-07 UTC: p95 402ms2026-09-08 UTC: p95 427ms2026-09-09 UTC: p95 435ms2026-09-10 UTC: p95 443ms2026-09-11 UTC: p95 403ms2026-09-12 UTC: p95 396ms2026-09-13 UTC: p95 410ms2026-09-14 UTC: p95 245ms2026-09-15 UTC: p95 450ms2026-09-16 UTC: p95 302ms2026-09-17 UTC: p95 420ms2026-09-18 UTC: p95 403ms2026-09-19 UTC: p95 439ms2026-09-20 UTC: p95 397ms2026-09-21 UTC: p95 470ms2026-09-22 UTC: p95 312ms2026-09-23 UTC: p95 376ms2026-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 380ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.7s2026-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.3s
Sep 6Sep 20Oct 5
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 708ms2026-09-10 UTC: p95 853ms2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.6s2026-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.2s
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 938ms2026-09-07 UTC: p95 668ms2026-09-08 UTC: p95 770ms2026-09-09 UTC: p95 862ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 939ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 869ms2026-09-16 UTC: p95 917ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 980ms2026-09-19 UTC: p95 920ms2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 927ms2026-09-22 UTC: p95 954ms2026-09-23 UTC: p95 1.1s2026-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.2s
Sep 6Sep 20Oct 5

Is it Zendesk, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Zendesk go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Zendesk, and again when they can reach it again. That is our own measurement from ten regions, not Zendesk's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 591msstatus code: 200checked: Oct 5, 2026, 7:58 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
      Operationallatency: 445msstatus code: 200checked: Oct 5, 2026, 8:17 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
      Operationallatency: 499msstatus code: 200checked: Oct 5, 2026, 7:24 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
      Operationallatency: 475msstatus code: 200checked: Oct 5, 2026, 7:37 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
    Operationallatency: 682msstatus code: 200checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 335msstatus code: 200checked: Oct 5, 2026, 7:56 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
      Operationallatency: 341msstatus code: 200checked: Oct 5, 2026, 8:05 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1000msstatus code: 200checked: Oct 5, 2026, 7:56 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
      Operationallatency: 1191msstatus code: 200checked: Oct 5, 2026, 7:24 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
      Operationallatency: 756msstatus code: 200checked: Oct 5, 2026, 7:30 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 outages

No outages on record yet for Zendesk.

measured 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 measurements and Zendesk's own claim at the time, side by side.

Full availability history for Zendesk: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Zendesk uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Zendesk's SLA implies, from our measurement

At or above your target

We measured none of downtime for Zendesk over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Zendesk; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.