- Level
- confirmed
- Worst impact
- Degraded
- Components
- API Servers
- Down Index
- 22of 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 1h 26m it lasted.
Anything that failed between 2026-10-08 08:28 UTC and 2026-10-08 09:54 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
It has been brought to our attention that a small number of clients are experiencing statusCode=500 errors when using our API. Our developers are investigating and we hope to have a solution shortly.
provider
- resolved
This incident has 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-a57077508d
Is SMTP2GO still down?
No, this incident was resolved 2026-10-08 09:54 UTC. For SMTP2GO's live state, see https://down.guide/smtp2go.
How long did it last?
1h 26m, from 2026-10-08 08:28 UTC to 2026-10-08 09:54 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.