State
Resolved
Started
89 d ago
2026-08-04 23:34 UTC
Lasted
37 min
until 2026-08-05 00:11 UTC
Worst impact
Partial outage
Timeline
0 updates23:3423:4323:5200:0100:11
Partial outageUpdate postedTimes in UTC
Resolved
37 min 100%
Updates
Times in UTCNo update text yet.
Affected components
4SupportTicketingAPIAgent Experience
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.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