Skip to main content
SMTP2GO

Inbound Server Issue

Partial outage Lasted 57m · started · SMTP2GO's page

Level
confirmed
Worst impact
Partial outage
Components
Email sending (SMTP service)
Down Index
31of 100

What to do

  • Check whether you use SMTP2GO Email sending (SMTP service). 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 57m it lasted.

    Anything that failed between 2026-04-15 16:26 UTC and 2026-04-15 17:23 UTC may need a replay.
  • Subscribe to SMTP2GO's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=smtp2go works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SMTP2GO 2

  1. investigating

    Our development team is currently investigating the inbound mail servers, which are experiencing an unusually high volume of traffic. Users may encounter delays in message delivery while we work to identify the root cause and restore normal performance.

    provider

  2. resolved

    Our development team has resolved the incident. Please allow some time for the backlog to clear.

    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-0772eec96b

Is SMTP2GO still down?

No, this incident was resolved 2026-04-15 17:23 UTC. For SMTP2GO's live state, see https://down.guide/smtp2go.

How long did it last?

57m, from 2026-04-15 16:26 UTC to 2026-04-15 17:23 UTC, by the times SMTP2GO posted.

What was affected?

SMTP2GO named Email sending (SMTP service).

What caused it?

SMTP2GO hasn't published a root cause. If it does, it shows here.

Where does this come from?

SMTP2GO's official status page, https://smtp2gostatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.