# Inbound Timeout

- Provider: [SMTP2GO](https://down.guide/smtp2go)
- Level: confirmed
- Impact: Degraded
- lasted 1h 52m
- started 2026-09-29 20:31 UTC
- Email sending (SMTP service)
- id: DWN-a1ae0f39cf
- Official page: https://stspg.io/6t6yhv56zphz

## Updates from SMTP2GO
### 2026-09-29 20:31 UTC: identified
Inbound processing time has decreased due to higher than usual demand. We are adding network capacity to address this.

### 2026-09-29 22:23 UTC: resolved
This incident has been resolved.

### 2026-09-29 22:54 UTC: postmortem
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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).
