Issues loading tickets in Zendesk Support
Zendesk Support had problems loading tickets. The incident affected the Support and Ticketing components. Zendesk reports that the incident is resolved. It lasted 2 hours and 15 minutes.
State
Resolved
Started
Lasted
2 h 15 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
2 h 15 min 100%
Updates
Times in UTCAs posted by Zendesk
Affected components
2Zendesk in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
18
Median duration
2 h 49 min
This incident
20% shorter than the median
Other Zendesk incidents
All incidentsZendesk·Access temporarily restricted errors
Zendesk Support and Agent Workspace (via Support) had access temporarily restricted errors. Zendesk reports that the incident is resolved. The outage lasted 87 minutes.
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.
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.
Zendesk·Multiple Products access issues in Pod26
Zendesk·Forethought Login Issues
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.
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.
https://outages.live/feed.xml?providers=zendesk/feed subscribe https://outages.live/feed.xml?providers=zendeskFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane