- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on SMTP2GO. 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 2025-09-07 23:30 UTC and 2025-09-07 23:30 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 1
- resolved
Between 21:30 UTC and 23:15 UTC on September 7, a server misconfiguration temporarily affected email delivery. A small number of emails were rejected with the error "550 From header sender domain not verified", or some bounced emails with a DMARC error (for domains with a DMARC policy of reject). The issue was resolved, and all services are fully operational. We apologize for any inconvenience this may have caused.
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-ae39d4a672
Is SMTP2GO still down?
No, this incident was resolved 2025-09-07 23:30 UTC. For SMTP2GO's live state, see https://down.guide/smtp2go.
How long did it last?
0m, from 2025-09-07 23:30 UTC to 2025-09-07 23:30 UTC, by the times SMTP2GO posted.
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.