- Level
- confirmed
- Worst impact
- Degraded
- Components
- API Servers
- Down Index
- 24of 100
What to do
Check whether you use SMTP2GO API Servers. 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 2h 38m it lasted.
Anything that failed between 2026-01-12 15:33 UTC and 2026-01-12 18:11 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
- investigating
We’re aware of an API issue when calling api.smtp2go.com/v3/email/send endpoint and the server is sending back an HTTP status Code 500 for certain emails. Our development team is investigating.
provider
- resolved
The underlying service the API uses to send emails had an intermittent fault, causing some communication issues between the services. This issue has now been resolved.
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-1e9add27be
Is SMTP2GO still down?
No, this incident was resolved 2026-01-12 18:11 UTC. For SMTP2GO's live state, see https://down.guide/smtp2go.
How long did it last?
2h 38m, from 2026-01-12 15:33 UTC to 2026-01-12 18:11 UTC, by the times SMTP2GO posted.
What was affected?
SMTP2GO named API Servers.
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.