outages.live
Live
ResendIncident ·

Microsoft 365 Incident

DegradedOfficial update
0

Resend reports degraded email delivery because Microsoft 365 currently cannot accept email. Resend tracks the problem as monitoring and continues to retry delivery. This is not a Resend incident.

State

Monitoring

Started

Ongoing for

21 min

Worst impact

Degraded

Timeline

1 update
19:2719:3219:3719:4219:48
DegradedUpdate postedTimes in UTC

Monitoring

21 min 100%

Updates

Times in UTC

As posted by Resend

Monitoring

[Microsoft 365 is currently experiencing an incident](https://status.cloud.microsoft/), which is degrading its ability to accept email. While this is not a Resend incident, it is possible to see an elevated amount of “Delivery Delay” events if Microsoft is unable to accept the email. With our Delivery Delayed events, we will retry delivery. Once Microsoft resolves its incident, sending to these addresses will return to normal.

Resend in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

19

Median duration

39 min

This incident

47% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 39 min
90 days agoToday

Other Resend incidents

All incidents

Resend·Delayed email status updates

Email status updates are processing normally again. All delayed updates have been delivered, and no data was lost.

Resolved

Resend·Intermittent latency spikes on our emails API

We have resolved the underlying issue and service has been resumed.

Resolved

Resend·Delayed new team provisioning and contact webhook delivery

We have resolved the underlying issue and service has been resumed.

Resolved

Resend·Delayed new team provisioning and contact webhook delivery

We have resolved the underlying issue and service has been resumed.

Resolved

Resend·Resend API with elevated error rate

We have resolved the underlying issue and service has been resumed

Resolved

Follow Resend

Your coding agent knows when Resend is down, and tells you when a failure is theirs, not yours. You can also get Resend 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 "resend" and tell me if Resend 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=resend
Slack
/feed subscribe https://outages.live/feed.xml?providers=resend

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane