SMTP2GO Outage History

37 incidents recorded over the last 365 days, 37 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded SMTP2GO Incident

SMTP2GO incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026API ErrorThis incident has been resolved.10h 11mResolved
Oct 15, 2026Softbounce ErrorsThis incident has been resolved.2h 20mResolved
Oct 8, 2026Issues with API- statusCode=500This incident has been resolved.1h 25mResolved
Oct 1, 2026Connectivity IssuesThis incident has been resolved.8h 25mResolved
Oct 1, 2026Connection issues and 'processed' emailsThis incident has been resolved.33 minResolved
Sep 30, 2026Issues connecting to mail.smtp2go.comThis incident has been resolved.8 minResolved
Sep 30, 2026Email Delivery Delays - AU RegionA small number of accounts in our AU region are still experiencing delays. Our developers are currently investigating.-50 minResolved
Sep 30, 2026Email Delivery Delays - AU RegionIt appears that a small number of accounts are still experiencing delays. Our developers are currently investigating.4h 57mResolved
Sep 29, 2026Inbound TimeoutWe 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…1h 51mResolved
Sep 25, 2026Connectivity issuesOur 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…6h 32mResolved
Sep 23, 2026"Activity" Reporting DelayThis incident has been resolved. If you encounter any emails displaying as “Processed” only moving forward, please reach out to our support team for assistance.7h 14mResolved
Sep 21, 2026Akamai/Linode DNS issue affecting users in EU/UKLinode UK has marked this issue as resolved. SMTP2GO dashboard Activity reports have also been updated.20 minResolved
Sep 21, 2026"Activity" Reporting DelayThis incident has been resolved.7h 46mResolved
Sep 4, 2026Delivery Delays – Emails to Microsoft Hosted Domains And Others Held as “Processed”This incident has been resolved and mail queues have returned to normal. Thank you for your patience.11h 42mResolved
Aug 27, 2026Connection Issues and Delivery DelaysThis 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…1h 6mResolved
Aug 27, 2026Delivery Delays – Emails Held as “Processed”This incident has been resolved.3h 19mResolved
Aug 18, 2026"Activity" Reporting Delay: EU CustomersThis incident has been resolved. If you still have emails showing as "Processed" only, please reach out to our support team who can assist further.13h 14mResolved
Jul 25, 2026Delay in Processing/Delivery of EmailsThis incident has been resolved.10h 58mResolved
Jul 1, 2026Messages Queued as 'Processed'This incident has been resolved.27 minResolved
Jun 25, 2026SMS messages marked as "Sending"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.7h 57mResolved
Jun 1, 2026Processed emails (EU)This incident has been resolved.3h 4mResolved
May 4, 2026Connection Failures and DelaysThis incident has been resolved.3h 25mResolved
Apr 30, 2026Processed Emails (AU)This incident has now been resolved. New emails should flow as normal. Previously processed emails may take a little longer to update.2h 9mResolved
Apr 30, 2026Email Delivery Delays - AU RegionThis incident has been resolved.1h 42mResolved
Apr 15, 2026Inbound Server IssueOur development team has resolved the incident. Please allow some time for the backlog to clear.56 minResolved
Mar 31, 2026Investigating Email Processing Delays (AU Region)This incident has been resolved.10h 44mResolved
Mar 2, 2026Network Connectivity IssuesThis incident is now resolved. We apologize for any inconvenience encountered. If you experience issues connecting to our servers, please reach out to our support team for further assistance.7h 8mResolved
Feb 26, 2026Delays sending to Microsoft-hosted domainsThis incident has been resolved.24h 6mResolved
Feb 13, 2026Activity Page HeadersThis incident has been resolved.13h 34mResolved
Feb 8, 2026Connectivity issues for "mail-au.smtp2go.com"This issue has now been resolved, and services are operating normally. We apologise for any inconvenience this may have caused. If you continue to experience any connection failures when connecting to…2h 53mResolved
Jan 22, 2026Delivery DelaysThis incident has been resolved.28h 42mResolved
Jan 20, 2026Login Page Loading IssuesThis issue was caused by network instability at Akamai/Linode datacenters in the EU. This has now been resolved as per their bulletin on the issue.12h 29mResolved
Jan 12, 2026API ErrorThe underlying service the API uses to send emails had an intermittent fault, causing some communication issues between the services. This issue has now been resolved.2h 38mResolved
Dec 11, 2025Connectivity issueThis incident has been resolved. It appears to be related to a recent database configuration change. Further investigations will take place to ensure stability and to prevent such an incident from happening again.14 minResolved
Nov 19, 2025Delivery DelaysThis incident has been resolved.1h 12mResolved
Nov 13, 2025Subaccounts: Verified Senders IssueThis incident has been resolved.7h 47mResolved
Nov 5, 2025Greylisting Issues with Microsoft/YahooThis incident has been resolved.183h 46mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next SMTP2GO incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This SMTP2GO Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SMTP2GO acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single SMTP2GO outage in this window ran 7d 15h, against a mean recovery of 11h 18m. If you depend on SMTP2GO in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.