outages.live
Live
MailgunIncident ·

Delivery Delays for Microsoft Mailbox Providers

NoticeOfficial update
0

Mailgun reports delivery delays to Microsoft mailbox providers. Messages are deferred because of this issue. Mailgun identified the problem and states that no mail is lost at this time.

State

Identified

Started

Ongoing for

1 h 12 min

Worst impact

Notice

Timeline

1 update
22:3822:5623:1423:3223:50
NoticeUpdate postedTimes in UTC

Identified

1 h 12 min 100%

Updates

Times in UTC

As posted by Mailgun

Identified

Delivery to Microsoft mailbox providers is currently experiencing issues. Messages are deferred and there is no mail loss at this time. We will provide updates as we receive more information.

Mailgun in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

9

Median duration

50 min

This incident

1.4× the median

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

7 h 14 min
median 50 min
90 days agoToday

Other Mailgun incidents

All incidents

Mailgun·Message Delays in US Regions

Mailgun reported message delays in US regions. The delays affected Outbound Delivery and Email Services - Outbound Delivery. Mailgun reported the incident as resolved. The incident lasted 73 minutes.

Resolved

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·Route delays in EU Region

This incident has been resolved.

Resolved

Mailgun·EU Messaging Outage

This incident has been resolved.

Resolved

Follow Mailgun

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane