Live  /  SMTP2GO  /  Incident

SMTP2GO: Issues with API- statusCode=500

SMTP2GO · smtp2go.comResolved2026-10-08 09:54 UTC
Public — what happened

Summary

SMTP2GO reported on October 8, 2026 at 08:28 UTC that some of its customers were getting server errors (status code 500) when making requests to its API. The company said a limited number of clients were affected and that its developers were looking into the problem. SMTP2GO did not publicly name a cause, and the incident was marked resolved at 09:54 the same day.

Affected

API Servers

As listed on SMTP2GO’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the SMTP2GO status & history page.

Related: SMTP2GO status & history. SquidGrid is not affiliated with SMTP2GO.