- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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-10-25 09:30 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 2
- investigating
We are experiencing a technical issue that might result in 401 errors while using the API. All of our engineers are working hard to fix the issue as soon as possible. We understand that you have emails to deliver and an apology will not mean much right now. But we wanted you to know that we are 100% focused on fixing the issue and ensuring this doesn’t happen in the future. Thank you for your understanding, The MailerSend team
provider
- resolved
The incident was solved. You should no longer receive 401 errors when calling the API.
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-4ed877fb5c
Is MailerSend still down?
No, this incident was resolved 2023-10-25 09:30 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-10-25 09:30 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.