Skip to main content
MailerSend

Technical issue on our SMTP proxy

Degraded Lasted 0m · started · MailerSend's page

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-09-04 14: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 1

  1. resolved

    Some of our users experienced a service interruption today between 4:30 and 5:10pm (GMT+2) when connecting to our SMTP proxy. After investigation, we found out the certificate on our SMTP proxy caused some clients problems when connecting, resulting in TLS-related exceptions being reported. The issue has now been resolved. We sincerely apologize for the inconvenience. Thank you for your understanding, The MailerSend team

    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-20ae40ea63

Is MailerSend still down?

No, this incident was resolved 2023-09-04 14: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-09-04 14: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.