State
Resolved
Started
45 d ago
2026-09-17 14:29 UTC
Lasted
3 h 57 min
until 2026-09-17 18:26 UTC
Worst impact
Degraded
Timeline
0 updatesResolved
3 h 57 min 100%
Updates
Times in UTCNo update text yet.
Affected components
3Zendesk in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
18
Median duration
2 h 12 min
This incident
1.8× the median
Other Zendesk incidents
All incidentsZendesk·Multiple Products access issues in Pod26
Zendesk·Forethought Login Issues
Zendesk·Some customers are encountering CF error messages accessing Zendesk Support
Zendesk·US-East degraded traffic
Zendesk·Support Search errors pod 27
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.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.
https://outages.cc/feed.xml?providers=zendesk/feed subscribe https://outages.cc/feed.xml?providers=zendeskFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane