Softbounce Errors
Last updateresolvedOct 15 · 17:23 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
Operational
5 components
checked Oct 24, 2026 8:25 AM UTC · SMTP2GO's official status page
SMTP2GO is up and running.
All components operational
Statusfield watches SMTP2GO alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
15 reports published by SMTP2GO in the last 30 days
When SMTP2GO breaks, it is typically resolved in 5h 11m — median across 5 resolved incidents over 30 days.
resolvedOct 15 · 17:23 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
ResolvedOct 15 · 17:23 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedOct 8 · 09:54 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
ResolvedOct 8 · 09:54 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedOct 1 · 21:04 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedOct 1 · 09:44 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedSep 30 · 11:37 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
ResolvedSep 30 · 11:37 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedSep 30 · 08:00 UTC
A small number of accounts in our AU region are still experiencing delays. Our developers are currently investigating.
Reported by SMTP2GO on their status page.
ResolvedSep 30 · 08:00 UTC
A small number of accounts in our AU region are still experiencing delays. Our developers are currently investigating.
Reported by SMTP2GO on their status page.
resolvedSep 30 · 05:25 UTC
It appears that a small number of accounts are still experiencing delays. Our developers are currently investigating.
Reported by SMTP2GO on their status page.
postmortemSep 29 · 22:54 UTC
We investigated reports of SMTP connection timeouts and found that some of our incoming mail servers had accumulated stuck mail-handling processes. These processes were consuming excessive processing power, reducing the servers’ capacity to handle other connections and potentially causing slow responses or timeouts. Our investigation identified a possible fault in the handling of an SMTP authentication method. Diagnostic checks showed a process attempting to respond after a connection had closed. We are investigating whether this caused the processes to become stuck; the exact trigger has not yet been confirmed. Actions removed the observed resource buildup, but we are continuing to monitor for recurrence. We are preparing mail-server software updates and assessing whether they address the underlying fault. We are also evaluating a safeguard to detect and clear stuck processes before they affect service.
Reported by SMTP2GO on their status page.
ResolvedSep 29 · 22:23 UTC
This incident has been resolved.
Reported by SMTP2GO on their status page.
resolvedSep 25 · 21:47 UTC
Our team has implemented several changes to improve frontend database efficiency and overall performance. Service has stabilized, and we are no longer seeing the timeouts or intermittent connection issues previously reported. We will continue to monitor performance closely.
Reported by SMTP2GO on their status page.
ResolvedSep 25 · 21:47 UTC
Our team has implemented several changes to improve frontend database efficiency and overall performance. Service has stabilized, and we are no longer seeing the timeouts or intermittent connection issues previously reported.We will continue to monitor performance closely.
Reported by SMTP2GO on their status page.