No impact incident
SMTP2GO: Issues with API- statusCode=500
Oct 8, 2026, 08:28 UTC
started
09:54 UTC
resolved
1 h 26 min
duration
Affected: API Servers
Current status of SMTP2GO: Operational — live SMTP2GO status
Timeline
- Oct 8, 2026, 08:28 UTCinvestigatingIt 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.
- Oct 8, 2026, 09:54 UTCresolvedThis incident has been resolved.
Updates as published by SMTP2GO (original).
Other services with incidents at the same time
- Box 09:27 UTC · [Critical] Issues with Multiple Box Services
- Signicat 09:00 UTC · Incident on 3rd party service - Data Verification - DK-CPR
- ElevenLabs 08:48 UTC · Music 2.5 endpoints performance degraded
- Scaleway 08:27 UTC · [Container Registry] Increase in 5xx errors on fr-par Container Registry
- Bynder 08:19 UTC · Issues with Upload in the Global region
- Mews 08:04 UTC · Mews POS unavailable
- Rapid7 08:00 UTC · Vulnerability Management Increased Latency
More SMTP2GO incidents
- October 15, 2026 Softbounce Errors
- October 1, 2026 Connectivity Issues
- October 1, 2026 Connection issues and 'processed' emails
- September 30, 2026 Issues connecting to mail.smtp2go.com
- September 30, 2026 Email Delivery Delays - AU Region
- September 29, 2026 Inbound Timeout