Mailgun's Outbound Delivery component broke twice on 12 November. The first incident delayed messages in US regions for 1h 13m, and the second, longer fault held up delivery to Microsoft mailbox providers for 20h 14m. Both were Mailgun's doing, not an issue on your end.
Started
18:52 UTC
Duration
Lasted 1h 13m
Source
IsDown
Next time
Mailgun is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Outbound Delivery
What happened?
Mailgun logged two separate incidents against Outbound Delivery on 12 November. The first started at 18:52 UTC under the title "Message Delays in US Regions". Mailgun said it was investigating at 18:52, identified the issue at 19:34, implemented a fix and began monitoring at 19:45, and marked it resolved at 20:05, a total of 1h 13m. The second incident started at 22:38 UTC, titled "Delivery Delays for Microsoft Mailbox Providers". Mailgun's first update said delivery to Microsoft mailbox providers was experiencing issues, that messages were deferred, and that there was no mail loss at that time. No further update was filed until resolution, 20h 14m later, when Mailgun reported that delivery rates had returned to normal but that some messages may have expired with status code 602, "Too old", and would need to be retried. That means some outbound mail was not delayed but dropped outright during that window. No user reports were filed during either window on the record. Mailgun's status page is the only account of the day. Over the last 90 days Mailgun logged 10 incidents with a median duration of 1 hour 1 minute, so the Microsoft delay was far longer than Mailgun's typical fault.
Learning
The record for this day has no our_probes entry, which tells you something on its own: an uptime check that pings Mailgun's API or dashboard would have stayed green through both incidents, because the fault sat in outbound mail delivery to specific regions and specific mailbox providers, not in Mailgun's service being reachable. A check against your own sending endpoint would show the same thing, green, because your product was up and accepting requests the whole time. The actual failure happened downstream, in the queue between Mailgun and Microsoft's mail servers, where messages sat deferred for over 20 hours before some expired and were dropped for good. That is a layer your own monitoring cannot see no matter how you configure it, because it depends on a third party's mailbox infrastructure and how Mailgun's queue handles a backlog against it. If you rely only on pinging your own systems, a delay like this one shows up as missing email in someone's inbox days later, with no alert and no obvious cause. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.