Zendesk lists these components: Support, Agent Workspace (via Support).

When did the incident start and end?

It started at 2026-11-13 18:46 UTC. This page shows the end time when Zendesk marks it resolved.

How do I get alerts for Zendesk?

Subscribe to the Zendesk live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Zendesk. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

ZendeskIncident ·

Access temporarily restricted errors

Q: What happened?

Zendesk reported "Access temporarily restricted errors" on its status page at 2026-11-13 18:46 UTC. Zendesk reports access temporarily restricted errors. The errors affect Support and Agent Workspace via Support. Zendesk is investigating the incident, which started at 18:46 UTC.

DegradedOfficial update

Zendesk reports access temporarily restricted errors. The errors affect Support and Agent Workspace via Support. Zendesk is investigating the incident, which started at 18:46 UTC.

State

Investigating

Started

Ongoing for

1 h 1 min

Worst impact

Degraded

Timeline

1 update

18:4619:0119:1619:3119:46

DegradedUpdate postedTimes in UTC

Investigating

1 h 1 min 100%

Updates

Times in UTC

As posted by Zendesk

Investigating

Affected components

SupportAgent Workspace (via Support)

Zendesk in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 58 min

This incident

66% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days

median 2 h 58 min

90 days agoToday

Other Zendesk incidents

All incidents

Zendesk·Mail Delivery issues using the Zendesk Microsoft Exchange Connector

Zendesk reports mail delivery issues with the Microsoft Exchange Connector. The issues affect Support and Email. Zendesk states that the outage is resolved. It lasted about 25 hours.

Resolved

Zendesk·AI Agents are unresponsive

Zendesk AI Agents did not respond. The problem also affected Core Services and the Dashboard. Zendesk reports that the incident is resolved. The outage lasted 5 hours and 6 minutes.

Resolved

Zendesk·Multiple Products access issues in Pod26

Resolved

Zendesk·Forethought Login Issues

Resolved

Zendesk·Some customers are encountering CF error messages accessing Zendesk Support

Resolved

Follow Zendesk

Your coding agent knows when Zendesk is down, and tells you when a failure is theirs, not yours. You can also get Zendesk incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zendesk" and tell me if Zendesk has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=zendesk

Slack

/feed subscribe https://outages.live/feed.xml?providers=zendesk

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane