Is Zendesk down?
Check if zendesk.com is down for everyone or just you
Zendesk is up
All four probe methods (HTTP/1.1, HTTP/2, browser User-Agent, and curl HEAD) reached the server. If you can't reach it, the issue is local, try flushing DNS, switching networks, or disabling a VPN.
Notify me
We'll ping you the next time Zendesk's status flips. One-shot subscription, no account required.
Webhook receives a JSON payload on every status transition. Fire-and-forget — no auth from us; the URL is its own secret.
Monitor Zendesk — freeOne click — the form comes prefilled. A free account saves 5 monitors with email alerts, checked every 5 minutes. Pro checks every minute — you'll usually know before your users do — and adds webhook + Discord alerts, a public status page, and no ads.
Embed a live status badge for Zendesk
Live SVG, refreshed every minute, no signup needed. Shows up / degraded / down straight from our probes.
Methodology
- Probe
- We send a GET request to the target URL with each probe method and time the full response.
- Counts as DOWN
- Every probe method fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- Counts as DEGRADED
- At least one probe method succeeds but at least one fails, the site is up but blocking or mishandling a specific request type.
- Detail
- Per-method results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
- Cadence
- Every 5 minutes, in parallel across 4 independent probe methods (HTTP/1.1 with strict TLS, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) from our edge network. We check probe diversity, not geography — if a site blocks a non-browser User-Agent or only speaks HTTP/1.1, the four cards show it.
- Rate-limited targets
- If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status, we do not flood the target to confirm the outage.
- Data source
- Our verdict is based on direct multi-method probes, every result above is a live network request, never a Twitter mention or DownDetector aggregate. User reports, when shown, appear separately below as a supplementary signal and are never used to determine the up/down verdict.
Common questions
Why is Zendesk down right now?
Zendesk outages are usually caused by server overloads, failed deployments, CDN or DNS problems, DDoS attacks, or regional internet routing issues. isitdown.io checks Zendesk via 4 probe methods (HTTP/1.1, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) simultaneously. If all 4 fail, Zendesk is down for everyone. If only some fail, Zendesk is up but blocking or mishandling a specific request type. If all pass but you still can't connect, the issue is on your local network, VPN, or DNS.
How can I check if Zendesk is down for everyone or just me?
Click "Check Zendesk now" above. isitdown.io pings zendesk.com via 4 probe methods in parallel and reports which ones succeeded. If all four pass, the issue is local, try flushing your DNS cache, switching networks, disabling your VPN, or using a different browser. If two or more methods fail, the outage is on Zendesk's side.
Is Zendesk having issues today?
The live response-time graph above shows the last 24 hours of real checks against zendesk.com. Each data point is an actual HTTP request from our monitoring system, not a third-party feed. Green means up, red means down. Spikes indicate slow responses. Bookmark this page to check back during future outages.
AWS