The issue has been resolved

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 2022-08-10 02: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

1. resolvedAug 10, 2022, 2:30 AM UTC

   Users were facing 500 server errors on the API and SMTP connections and as a result, were unable to send some emails. The issue has been resolved. Thank you so much for your patience. We sincerely apologize for the inconvenience. A full explanation of what happened is on the way.

   provider

2. resolvedAug 10, 2022, 7:52 AM UTC

   Users have faced a lot of 500 server errors from 2:46 am UTC on the morning of 10th Oct, 22. SRE has been paged at 4:31 am UTC and noticed it was a storage issue. The storage caused errors while creating new files in storage for cache or message content, etc. Our SRE team started cleaning up the storage at 4:57 am UTC and put mitigation measures in place so storage utilization would be better managed and would send alerts in case of failure.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.