Erroneous "user not found" Responses for Apple iCloud and Private Relay Addresses
Mailgun returns erroneous "user not found" responses for Apple iCloud and Private Relay addresses. Mailgun reports that it removes the affected addresses from suppression lists and monitors the deliverability. The incident is still open.
State
Monitoring
Started
Ongoing for
18 h 21 min
Worst impact
Notice
Timeline
2 updatesIdentified
7 h 29 min 41%
Monitoring
10 h 52 min 59%
Updates
Times in UTCAs posted by Mailgun
Addresses that were impacted are in the process of being removed from suppression lists.
We are currently monitoring the deliverability of Apple iCloud and Private Relay addresses. We working on removing addresses that were added to suppression lists during the effected time.
Mailgun in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
1 h 1 min
This incident
18× the median
Other Mailgun incidents
All incidentsMailgun·Delivery Delays for Microsoft Mailbox Providers
Mailgun reported delivery delays to Microsoft mailbox providers. Messages were deferred with no mail loss. Mailgun later reported that delivery rates returned to normal, and the incident is resolved after about 20 hours.
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.
Mailgun·Route delays in EU Region
This incident has been resolved.
Mailgun·Route delays in EU Region
This incident has been resolved.
Mailgun·Route delays in EU Region
This incident has been 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.
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.
https://outages.live/feed.xml?providers=mailgun/feed subscribe https://outages.live/feed.xml?providers=mailgunFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane