AI Agents are unresponsive
Major outageOfficial update
0
Zendesk reports that AI Agents do not respond. The problem also affects Core Services and the Dashboard. Zendesk is investigating the incident.
State
Investigating
Started
Ongoing for
2 h 7 min
Worst impact
Major outage
Timeline
1 update10:3911:1111:4212:1412:46
Major outageUpdate postedTimes in UTC
Investigating
2 h 7 min 100%
Updates
Times in UTCAs posted by Zendesk
Investigating
Affected components
3AI AgentsCore ServicesDashboard
Zendesk in the last 90 days
Full history90 days agoToday
Incidents in 90 days
13
Days with an incident
17
Median duration
2 h 26 min
This incident
About the median
Other Zendesk incidents
All incidentsFollow 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.cc/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.cc/feed.xml?providers=zendeskSlack
/feed subscribe https://outages.cc/feed.xml?providers=zendeskFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane