Inbound Timeout

What to do

• Check whether you use SMTP2GO Email sending (SMTP service). Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 52m it lasted.

  Anything that failed between 2026-09-29 20:31 UTC and 2026-09-29 22:23 UTC may need a replay.

• Subscribe to SMTP2GO's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=smtp2go works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SMTP2GO 3

1. identifiedSep 29, 2026, 8:31 PM UTC

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

   provider

2. resolvedSep 29, 2026, 10:23 PM UTC

   This incident has been resolved.

   provider

3. postmortemSep 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.