Historial de interrupciones de Smtp2go

1. September 4, 2026 at 8:58 AM UTCinvestigating

   Nuestro equipo está actualmente investigando un problema que hace que algunos correos electrónicos permanezcan en el estado “Procesado” a direcciones de correo electrónico de Microsoft, lo que da lugar a retrasos de entrega y lista gris. Estamos trabajando para resolver el problema. Recomendamos la inclusión segura siempre que sea posible: https://support.smtp2go.com/hc/en-gb/articles/360000471954-Allowlisting-IP-Addresses-with-Microsoft-365

2. September 4, 2026 at 11:17 AM UTCidentified

   Mientras seguimos manejando el problema en curso con dominios de Microsoft, todos los indicadores apuntan a un problema global más grande con Microsoft mismo. Seguiremos proporcionando actualizaciones ya que están disponibles. https://groups.io/email-provider-status?isp=Microsoft+365

3. September 4, 2026 at 12:04 PM UTCidentified

   Microsoft ha aceptado la responsabilidad de los actuales retrasos de correo electrónico. Más detalles se pueden encontrar en su página de estado y abajo: ID de edición: EX1467029 Servicios afectados: Intercambio en línea Estado: Degradación de los servicios Tipo de edición: incidentes Hora de inicio: Sep 4, 2026, 10:19 GMT+12 Impacto del usuario Los usuarios pueden experimentar un retraso en el envío y recepción de mensajes de correo electrónico de dominios externos en Exchange Online. Más info Los usuarios pueden experimentar errores intermitentes “Server ocupado”, afectando múltiples buzones de correo. Alcance de los efectos Este problema afecta a los usuarios que pueden estar intentando enviar y recibir mensajes de correo electrónico de dominios externos en Exchange Online. Esta información puede actualizarse a medida que continúe nuestra investigación.

4. September 4, 2026 at 2:04 PM UTCidentified

   Estamos investigando ya que este tema ha comenzado a afectar a otros proveedores, como Gmail

5. September 4, 2026 at 2:26 PM UTCinvestigating

   Nuestro equipo técnico está investigando un problema con algunos mensajes a varios proveedores que se muestran como "Procesos" y no llegan al receptor

6. September 4, 2026 at 2:38 PM UTCmonitoring

   La carga excesiva del servidor causada por el golpe en los efectos del problema del servicio de Microsoft causó colas externas anormales. Se ha implementado una solución y estamos monitoreando las colas del servidor

7. September 4, 2026 at 8:41 PM UTCresolved

   Este incidente se ha resuelto y las colas de correo han vuelto a la normalidad. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 27, 2026 at 10:38 PM UTCidentified

   Hemos identificado el problema que hace que algunos clientes experimenten problemas de conexión y retrasos de entrega (con correos electrónicos restantes en el estado “Procesado”. Nuestro equipo está trabajando con urgencia para resolver el problema y restaurar el servicio normal.

2. August 27, 2026 at 11:01 PM UTCmonitoring

   Se ha aplicado una solución y seguimos vigilando los resultados. La estabilidad de conexión está mejorando, los niveles de cola están disminuyendo y se están procesando correos electrónicos retrasados.

3. August 27, 2026 at 11:21 PM UTCmonitoring

   Seguimos vigilando la situación. Si sigues experimentando problemas de conexión o retrasos de entrega, por favor contacta con nuestro equipo de apoyo para recibir asistencia.

4. August 27, 2026 at 11:44 PM UTCresolved

   Este incidente ha sido resuelto. Sinceramente nos disculpamos por la perturbación e inconveniencia causadas. Si experimenta otros problemas con la conexión o la entrega de correo electrónico, por favor contacte con nuestro equipo de soporte para recibir asistencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 27, 2026 at 3:20 AM UTCinvestigating

   Nuestro equipo está actualmente investigando un problema que hace que algunos correos electrónicos permanezcan en el estado “Procesado”, dando lugar a retrasos en la entrega. Estamos trabajando para resolver el problema.

2. August 27, 2026 at 3:57 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. August 27, 2026 at 4:52 AM UTCmonitoring

   Se ha aplicado una solución, y estamos monitoreando los resultados. El atraso de los correos electrónicos mantenidos en el estado “Procesado” se está trabajando ahora.

4. August 27, 2026 at 5:18 AM UTCmonitoring

   Seguimos monitoreando.

5. August 27, 2026 at 6:40 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 18, 2026 at 4:47 PM UTCinvestigating

   Los usuarios europeos pueden experimentar un retraso en la actualización de los estados de entrega en el panel. Nuestros desarrolladores están trabajando actualmente en una solución. Tenga la seguridad de que los correos electrónicos han sido entregados con éxito a pesar de las actualizaciones de estado retrasados.

2. August 19, 2026 at 6:01 AM UTCresolved

   Este incidente ha sido resuelto. Si todavía tiene correos electrónicos mostrando como "Procesado" sólo, por favor contacte a nuestro equipo de soporte que puede ayudar más.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 25, 2026 at 7:01 PM UTCinvestigating

   Nuestros desarrolladores están investigando un problema causando retrasos en el procesamiento de correo electrónico. Algunos usuarios en el servidor afectado pueden ver correos electrónicos impares atrapados en la etapa "Procesado" en su página de Actividad, mientras que otros están siendo entregados.

2. July 26, 2026 at 6:00 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 1, 2026 at 9:42 AM UTCinvestigating

   We are currently investigating an issue with email delivery

2. July 1, 2026 at 10:01 AM UTCmonitoring

   The issue has been identified and addressed

3. July 1, 2026 at 10:10 AM UTCresolved

   This incident has been resolved.

1. June 25, 2026 at 10:32 AM UTCidentified

   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/

2. June 25, 2026 at 12:20 PM UTCidentified

   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/

3. June 25, 2026 at 5:27 PM UTCmonitoring

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

4. June 25, 2026 at 5:27 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. June 25, 2026 at 6:29 PM UTCresolved

   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.

1. June 1, 2026 at 7:31 AM UTCinvestigating

   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.

2. June 1, 2026 at 8:48 AM UTCinvestigating

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

3. June 1, 2026 at 9:18 AM UTCidentified

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

4. June 1, 2026 at 9:40 AM UTCidentified

   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.

5. June 1, 2026 at 9:41 AM UTCmonitoring

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

6. June 1, 2026 at 10:35 AM UTCresolved

   This incident has been resolved.

1. May 4, 2026 at 7:04 PM UTCinvestigating

   Degraded performance of US inbound servers is causing processing delays, intermittent timeouts and incorrect "421 Too many concurrent SMTP connections from this IP address; please try again later." errors. This is isolated to US-based servers. If you are experiencing any of these issues, please try changing the server name to mail-eu.smtp2go.com until further notice.

2. May 4, 2026 at 10:29 PM UTCresolved

   This incident has been resolved.

1. April 30, 2026 at 6:25 AM UTCidentified

   Some users may experience delays and see "Processed" emails on their Activity feed. Our developers have identified the issue and are implementing a fix.

2. April 30, 2026 at 8:35 AM UTCresolved

   This incident has now been resolved. New emails should flow as normal. Previously processed emails may take a little longer to update.

1. April 30, 2026 at 3:35 AM UTCinvestigating

   We are aware of an issue where some emails are currently stuck in the "Processed" status. Our team is actively taking steps to resolve the issue as quickly as possible.

2. April 30, 2026 at 4:00 AM UTCmonitoring

   A fix has been deployed and we're continuing to monitor the situation. We are seeing email queues begin to clear and expect all delayed messages to be delivered shortly. Thank you for your patience, and we apologise for the inconvenience.

3. April 30, 2026 at 5:17 AM UTCresolved

   This incident has been resolved.

1. April 15, 2026 at 4:26 PM UTCinvestigating

   Our development team is currently investigating the inbound mail servers, which are experiencing an unusually high volume of traffic. Users may encounter delays in message delivery while we work to identify the root cause and restore normal performance.

2. April 15, 2026 at 5:23 PM UTCresolved

   Our development team has resolved the incident. Please allow some time for the backlog to clear.

1. March 31, 2026 at 11:08 PM UTCinvestigating

   We are investigating an issue causing delays in email delivery in the AU region. These emails will appear as "Processed" on the "Reports > Activity" page. Our engineering team is currently working to identify the root cause and restore normal processing speeds as quickly as possible.

2. March 31, 2026 at 11:58 PM UTCidentified

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

3. April 1, 2026 at 2:09 AM UTCidentified

   A preliminary fix is being implemented and the backlog of processed email is being worked through.

4. April 1, 2026 at 5:28 AM UTCmonitoring

   A resolution has been implemented and we're continuing to monitor. While the backlog of "Processed" emails is clearing, clients may notice a temporary delay in event updates (such as the "Delivered" status) appearing in the Activity page reporting. These records are being processed and will be fully updated shortly.

5. April 1, 2026 at 9:53 AM UTCresolved

   This incident has been resolved.

1. March 2, 2026 at 5:00 PM UTCinvestigating

   We are investigating a system-wide outage. Users may experience connectivity issues. Please try connecting to mail-us.smtp2go.com or mail-eu.smtp2go.com in the meantime.

2. March 2, 2026 at 10:36 PM UTCmonitoring

   A fix has been implemented, and we are continuing to monitor.

3. March 3, 2026 at 12:08 AM UTCresolved

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

1. February 26, 2026 at 3:01 AM UTCmonitoring

   We are currently aware of a global issue affecting emails sent to Microsoft-hosted domains (such as hotmail.com, outlook.com, live.com, etc.). Emails affected will show as "Processed" on the "Reports > Activity" page, and delivery attempts encounter "451 4.7.650……….." responses. This is a Microsoft-wide issue affecting multiple SMTP providers/ESPs, and we are monitoring it closely as they actively work on a fix. Thanks for your patience.

2. February 27, 2026 at 3:08 AM UTCresolved

   This incident has been resolved.

1. February 13, 2026 at 2:36 PM UTCidentified

   We have identified an issue with headers for sent messages not displaying in the Activity page. We are investigating and will update.

2. February 14, 2026 at 4:10 AM UTCresolved

   This incident has been resolved.

1. February 8, 2026 at 11:57 PM UTCidentified

   Some customers may experience intermittent connection failures when connecting to "mail-au.smtp2go.com". Our development team has identified the issue and is taking corrective action to restore full stability as quickly as possible. Recommended Action: While we resolve this, you can maintain a stable connection by switching your SMTP server address to "mail.smtp2go.com".

2. February 9, 2026 at 2:51 AM UTCresolved

   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 "mail-au.smtp2go.com", please reach out to our support team for assistance.

1. January 22, 2026 at 7:44 PM UTCinvestigating

   We are currently investigating an issue affecting the mail servers. During this time, users may experience delays in email delivery.

2. January 22, 2026 at 8:02 PM UTCidentified

   Our team has identified a global service outage affecting Microsoft. As a result, outbound emails to Microsoft-hosted domains may be delayed. We are securely holding affected messages and will continue to automatically re-attempt delivery until Microsoft resolves the issue.

3. January 24, 2026 at 12:26 AM UTCresolved

   This incident has been resolved.

1. January 20, 2026 at 3:27 PM UTCinvestigating

   Some customers are experiencing issues loading the SMTP2GO login page. Please try logging in at https://app-us.smtp2go.com/login/ while we investigate this issue

2. January 20, 2026 at 4:08 PM UTCinvestigating

   We are continuing to investigate this issue. If you cannot log in, please try using: https://app-us.smtp2go.com/login/

3. January 21, 2026 at 3:57 AM UTCresolved

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

1. January 12, 2026 at 3:33 PM UTCinvestigating

   We’re aware of an API issue when calling api.smtp2go.com/v3/email/send endpoint and the server is sending back an HTTP status Code 500 for certain emails. Our development team is investigating.

2. January 12, 2026 at 6:11 PM UTCresolved

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