outages.live
Live
ZendeskIncident ·

Mail Delivery issues using the Zendesk Microsoft Exchange Connector

Partial outageOfficial update
0

Zendesk Mail Delivery does not work for some users of the Zendesk Microsoft Exchange Connector. Support and Email are affected. Zendesk identified the problem.

State

Identified

Started

Ongoing for

1 h 33 min

Worst impact

Partial outage

Timeline

1 update
18:1518:3819:0119:2419:48
Partial outageUpdate postedTimes in UTC

Identified

1 h 33 min 100%

Updates

Times in UTC

As posted by Zendesk

Identified

Affected components

2
SupportEmail

Zendesk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

13

Days with an incident

17

Median duration

2 h 49 min

This incident

45% 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 49 min
90 days agoToday

Other Zendesk incidents

All incidents

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

Zendesk·US-East degraded traffic

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