- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 100
What to do
Check whether your product depends on MailerSend. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-02-19 15:35 UTC and 2023-04-12 16:52 UTC may need a replay.Subscribe to MailerSend's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mailersend works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from MailerSend 3
- monitoring
We experienced a technical issue during our release, which caused an outage on our sending servers. Our engineers worked on a fix as soon as we identified the root cause. This incident happened at 10:36 am UTC+2 and resulted in losing emails sent with our SMTP relay. We apologize for this downtime. We know you have emails to deliver, so we have been 100% focused on resolving this and preventing future issues. You can check the status page for regular updates. We appreciate your understanding, The MailerSend team
provider
- monitoring
SMTP is now operational.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b1205f8a54
Is MailerSend still down?
No, this incident was resolved 2023-04-12 16:52 UTC. For MailerSend's live state, see https://down.guide/mailersend.
How long did it last?
0m, from 2026-02-19 15:35 UTC to 2023-04-12 16:52 UTC, by the times MailerSend posted.
What caused it?
MailerSend hasn't published a root cause. If it does, it shows here.
Where does this come from?
MailerSend's official status page, https://status.mailersend.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.