SMTP2GO

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.

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

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.

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

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.

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

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.

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

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