Mailgun had 41 outages in the last 2 years totaling 70h 20m of downtime — averaging 1.7 incidents per month.
There were 41 Mailgun outages since September 30, 2024 totaling 70h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. No other email providers are currently affected.
We are continuing to monitor for any further issues.
Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally.
Mailgun is monitoring service impacts in GCP's us-west1 region. We are routing traffic away from impacted infrastructure. Currently we are seeing delays in log processing and a small number of message sends.
Outbound delivery is operating normally. Currently there are delays for event logs and some webhooks.
GCP has put a mitigation in place, we are monitoring the results. At this time we are experiencing no impacts. All delayed webhooks and logs have been processed.
This incident has been resolved.
We have received confirmation that an external issue impacting email delivery to Microsoft 365 domains has been resolved. Impacted messages would have received an error stating "5.7.511 Access denied, banned sender" between Friday, August 14th and Monday, August 17th. Any failed messages will need to be resent. Information on retrying messages can be found in our Help Center here: https://help.mailgun.com/hc/en-us/articles/18596982041883-Resending-messages
We are currently experiencing a denial of service attack against our click and open tracking servers. Remediation work is underway. Some requests may time out or fail at this time.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix is in the process of being rolled out to impacted regions.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with email previews not working. Outbound processing, inbound processing, logs and webhook delivery are operating normally.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers using the events/logs APIs or viewing logs in the customer portal may see delays in some events appearing. These delays are only affecting a subset of our customers.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers creating domains with Automatic Sender Security may have CNAME records with no corresponding TXT records reflecting DKIM keys. A fix for this issue is being prepared.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue where customers making HTTPS requests to our API without Server Name Indication (SNI) enabled are being presented with an expired SSL/TLS certificate. This results in certificate validation failures for affected clients.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Elevated 500 errors beginning at 17:25 UTC resolved at 17:30 UTC
Some requests may be incorrectly failing with 401 error codes in our US region.
A fix has been deployed and systems are back to normal.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
Domain verification is also impacted. Increased chances of domain verification failing. The issue has been identified and engineering is actively working on a fix.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Logs are currently experiencing delays of 15 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.
Logs are currently experiencing delays of 20 minutes in Mailgun's EU region. Outbound processing, inbound processing, and webhook delivery are operating normally.
This incident has been resolved.
Logs are currently experiencing delays of 15 minutes in Mailgun's US region. Outbound processing, inbound processing, and webhook delivery are operating normally.
Events are processing normally, we continue to monitor as we see elevated send volumes.
Events are processing normally.
On November 13th, Mailgun incorrectly rejected a subset of inbound emails with a 550 "recipient rejected" error. Senders received bounce notifications even though delivery should have succeeded. Affected timeframes: US region: 05:14 to 06:41 UTC and 14:55 to 15:48 UTC EU region: 14:55 to 15:48 UTC Based on our analysis, approximately 25% of US inbound traffic and 50% of EU inbound traffic had a chance to have been impacted during these windows. We're unable to provide exact counts due to gaps in our logging for rejected inbound mail, which we have since corrected.
We have identified processing delays for some messages in our US region. A fix has been deployed and we are monitoring the recovery.
Queues are being worked through, we continue to monitor resolution.
Operations are back to normal and queues are cleared. We'll continue to monitor.
This incident has been resolved.