Live / SMTP2GO / Incident
SMTP2GO: Softbounce Errors
SMTP2GO · smtp2go.comMajor incidentResolved2026-10-15 17:23 UTC
Public — what happened
Summary
SMTP2GO reported a major incident on October 15, 2026, beginning at 15:03 UTC, in which some email sent through its service was being soft-bounced. The company said a recent change to how its servers handle traffic was involved: an Exim patch aimed at "SMTP smuggling" changed what happens when a message's line endings lack a required carriage-return character. While it considered reversing that update, SMTP2GO advised customers to connect to one of three specific IP addresses instead of the usual mail.smtp2go.com hostname as a temporary workaround. The incident was marked resolved at 17:23 the same day.
Affected
Email sending (SMTP service)
Timeline
- Started — 2026-10-15 15:03 UTC
- Investigating — 2026-10-15 15:03 UTC
- Resolved — 2026-10-15 17:23 UTC · 2h 20m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach SMTP2GO against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for SMTP2GO: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the SMTP2GO report →
More from SMTP2GO
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.