Live / SMTP2GO / Incident
SMTP2GO: API Error
SMTP2GO · smtp2go.comMinor incidentResolved2026-10-30 23:20 UTC
Public — what happened
Summary
SMTP2GO reported a minor problem with its API, in which some attempts to send email returned an error saying the message could not be queued at that time. The company said it began looking into it at 13:08 UTC on 2026-10-30 and asked affected customers to turn off the FastAccept setting for the time being. The update does not name a cause, and the incident is marked resolved as of 23:20 on the same day.
Affected
API Servers
Timeline
- Started — 2026-10-30 13:08 UTC
- Investigating — 2026-10-30 13:08 UTC
- Resolved — 2026-10-30 23:20 UTC · 10h 12m 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 45, 2026, our weekly internet health report.