Smtp2go outage history

The team recently updated how our servers process traffic. Specifically, SMTP (https://www.rfc-editor.org/info/rfc5321/#section-2.3.8) requires 0x0d immediately before 0x0a; a recent patch to Exim against "SMTP smuggling" has altered its behavior when it encounters a missing 0x0d. The team is looking into rolling back this update, but in the meantime, we are suggesting connecting to 45.33.50.34, 43.228.184.6, or 45.33.53.153 instead of the mail.smtp2go.com hostname as a potential workaround.

This incident has been resolved.

It 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.

This incident has been resolved.

Our development team is continuing to investigate the connectivity issues. In the meantime, please try connecting through mail-eu.smtp2go.com or mail-us.smtp2go.com. We also recommend safelisting our new inbound IP addresses, which are listed here: https://support.smtp2go.com/hc/en-gb/articles/227835308-Worldwide-Server-Locations-IP-Addresses-and-Email-Routing

This incident has been resolved.

Our team has been adding new servers to increase capacity, which caused some connection issues and 'processed' emails earlier today. This has been addressed now. Please let us know if you continue seeing any issues.

This incident has been resolved.

If you're having trouble connecting to mail.smtp2go.com, try connecting to mail-eu.smtp2go.com instead. Some European locations can't resolve to mail.smtp2go.com. This is a temporary issue that should be fixed shortly. Also, please check that no firewalls are blocking connections to the new IPs we've added to mail.smtp2go.com. The IPs can be found here: https://support.smtp2go.com/hc/en-gb/articles/227835308-Worldwide-Server-Locations-IP-Addresses-and-Email-Routing

This incident has been resolved.

A small number of accounts in our AU region are still experiencing delays. Our developers are currently investigating.

A small number of customers in our AU region may be experiencing email delivery delays, with emails being held as “Processed”. Our development team is actively investigating the issue and working to resolve it as a matter of urgency. We apologise for any inconvenience and will provide further updates as more information becomes available.

The issue has been identified, and a fix is being deployed currently. "Processed" emails will begin flowing through shortly.

A fix has been deployed, and the mail queue is dropping. We're continuing to monitor.

"Processed" emails are continuing to flow through successfully. Some emails remain queued, and we're continuing to monitor as these clear.

It appears that a small number of accounts are still experiencing delays. Our developers are currently investigating.

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

This incident has been resolved.

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.

Some customers are experiencing timeouts and intermittent connection issues. We have deployed a planned frontend database speed improvement and are actively monitoring performance while continuing to investigate.

Our team has implemented several changes to improve frontend database efficiency and overall performance. Service has stabilized, and we are no longer seeing the timeouts or intermittent connection issues previously reported. We will continue to monitor performance closely.

Users may notice that delivered emails are currently displaying as “Processed” within their Activity feeds. Our development team is actively investigating the issue and working to identify the cause

A fix has been implemented and we are monitoring the results.

This incident has been resolved. If you encounter any emails displaying as “Processed” only moving forward, please reach out to our support team for assistance.

This incident was caused by a DNS incident at the Akamai/Linode data center in London. More detail can be found here: https://status.linode.com/incidents/fsgmc1p06swx Impact on customers is limited to delays to updates on the Activity/Delivery reporting.

Linode UK has marked this issue as resolved. SMTP2GO dashboard Activity reports have also been updated.

Users may notice that delivered emails are currently displaying as “Processed” within their Activity feeds. Our development team is actively investigating the issue and working to identify the cause

This incident has been resolved.

Our team is currently investigating an issue causing some emails to remain in the “Processed” state to Microsoft email addresses, resulting in delivery delays and greylisting. We are working to resolve the issue. We recommend safelisting wherever possible: https://support.smtp2go.com/hc/en-gb/articles/360000471954-Allowlisting-IP-Addresses-With-Microsoft-365

While we continue to handle the ongoing issue with Microsoft domains, all indicators point to a larger, global issue with Microsoft itself. We will continue providing updates as they are available. https://groups.io/email-provider-status?isp=Microsoft+365

Microsoft has accepted responsibility for the current email delays. More details can be found on their status page and below: Issue ID: EX1467029 Affected services: Exchange Online Status: Service degradation Issue type: Incident Start time: Sep 4, 2026, 10:19 PM GMT+12 User impact Users may experience a delay in sending and receiving email messages from external domains in Exchange Online. More info Users may experience intermittent “Server busy” errors, affecting multiple mailboxes. Scope of impact This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.

We are investigating as this issue has now started affecting other providers, like Gmail

Our technical team is investigating an issue with some messages to various providers being shown as "Processed" and not reaching the recipient

Excess server burden caused by knock on effects from the Microsoft service issue caused abnormal outbound queues. A fix has been implemented and we are monitoring server queues

This incident has been resolved and mail queues have returned to normal. Thank you for your patience.

We have identified the issue causing some customers to experience connection issues and delivery delays (with emails remaining in the “Processed” state). Our team is working with urgency to resolve the issue and restore normal service.

A fix has been implemented, and we are continuing to monitor the results. Connection stability is improving, queue levels are dropping, and delayed emails are being processed.

We are continuing to monitor the situation. If you are still experiencing connection issues or delivery delays, please reach out to our support team for assistance.

This incident has been resolved. We sincerely apologise for the disruption and inconvenience caused. If you experience any further issues with connecting or email delivery, please reach out to our support team for assistance.

Our team is currently investigating an issue causing some emails to remain in the “Processed” state, resulting in delivery delays. We are working to resolve the issue.

We are continuing to investigate this issue.

A fix has been implemented, and we are monitoring the results. The backlog of emails held in the “Processed” state is now being worked through.

We are continuing to monitor.

This incident has been resolved.

European users may experience a delay in delivery statuses being updated in the dashboard. Our developers are currently working on a fix. Please rest assured that the emails have been delivered successfully despite the delayed status updates.

This incident has been resolved. If you still have emails showing as "Processed" only, please reach out to our support team who can assist further.

Our developers are investigating an issue causing delays in email processing. Some users on the affected server may see odd emails stuck in the "Processed" stage on their Activity page, whilst others are being delivered.

This incident has been resolved.

We are currently investigating an issue with email delivery

The issue has been identified and addressed

This incident has been resolved.

Our SMS partner Message Media is experiencing issues which is resulting in some SMS messages being marked as "Sending". You can subscribe to updates on their status page here: https://status.messagemedia.com/

We are still waiting for more details from our SMS partner, Message Media. You can subscribe to updates on their status page here: https://status.messagemedia.com/

Our provider has confirmed that a fix has been implemented and they are monitoring the results: https://status.messagemedia.com/

We are continuing to monitor for any further issues.

A fix has been implemented, and messaging services have recovered. We have completed validation testing and confirmed that message sending and delivery are functioning as expected.

We are aware of an issue causing delays in email delivery. Affected emails will appear as "Processed" in the Activity feed. Our development team is investigating and working to resolve the issue.

We are continuing to investigate this issue at the highest priority level.

The issue has been identified and a fix is being implemented.

The issue has been identified as a failed server that did not have an easy mitigation strategy for its failure, as it was part of an older network configuration. Measures have been put in place to re-route traffic and some delays are anticipated while the backlog gets processed. This is not anticipated to be long. We will have a full review of our strategy around this with the view to eliminate this from happening in the future.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.