SMTP2GO incident

Inbound Timeout

Minor Resolved View vendor source →

SMTP2GO experienced a minor incident on September 29, 2026 affecting Email sending (SMTP service), lasting 1h 51m. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2026, 08:31 PM UTC
Resolved
Sep 29, 2026, 10:23 PM UTC
Duration
1h 51m
Detected by Pingoru
Sep 29, 2026, 08:31 PM UTC

Affected components

Email sending (SMTP service)

Update timeline

  1. identified Sep 29, 2026, 08:31 PM UTC

    Inbound processing time has decreased due to higher than usual demand. We are adding network capacity to address this.

  2. resolved Sep 29, 2026, 10:23 PM UTC

    This incident has been resolved.

  3. postmortem Sep 29, 2026, 10:54 PM UTC

    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.