Histórico de interrupções do Smtp2go

1. 4 Gwengolo 2026 da 08:58 UTCinvestigating

   Nossa equipe está atualmente investigando um problema que faz com que alguns e-mails permaneçam no estado "Processado" para endereços de e-mail da Microsoft, resultando em atrasos na entrega e na listagem cinzenta. Estamos a trabalhar para resolver a questão. Recomendamos listagem segura sempre que possível: https://support.smtp2go.com/hc/en-gb/articles/360000471954-Allowlisting-IP-Addres-With-Microsoft-365

2. 4 Gwengolo 2026 da 11:17 UTCidentified

   Enquanto continuamos a lidar com o problema contínuo com os domínios da Microsoft, todos os indicadores apontam para um problema maior e global com a própria Microsoft. Continuaremos a fornecer atualizações já que estão disponíveis. https://groups.io/email-provider-status?isp=Microsoft+365

3. 4 Gwengolo 2026 da 12:04 UTCidentified

   A Microsoft aceitou a responsabilidade pelos atrasos de e-mail atuais. Mais detalhes podem ser encontrados em sua página de status e abaixo: ID de emissão: EX1467029 Serviços afetados: Exchange Online Estado: degradação do serviço Tipo de problema: Incidente Hora de início: Sep 4, 2026, 10:19 GMT+12 Impacto do utilizador Os usuários podem ter um atraso no envio e recebimento de mensagens de e-mail de domínios externos no Exchange Online. Mais informações Os usuários podem experimentar erros intermitentes de "Servir ocupado", afetando várias caixas de correio. Âmbito de aplicação Este problema impacta os usuários que podem estar tentando enviar e receber mensagens de e-mail de domínios externos no Exchange Online. Essas informações podem ser atualizadas conforme nossa investigação continua.

4. 4 Gwengolo 2026 da 14:04 UTCidentified

   Estamos investigando como esta questão começou a afetar outros provedores, como o Gmail

5. 4 Gwengolo 2026 da 14:26 UTCinvestigating

   Nossa equipe técnica está investigando um problema com algumas mensagens para vários provedores sendo mostrado como "Processado" e não atingindo o destinatário

6. 4 Gwengolo 2026 da 14:38 UTCmonitoring

   O excesso de carga do servidor causado pela batida sobre os efeitos do problema de serviço da Microsoft causou filas de saída anormais. Foi implementada uma correção e estamos monitorando filas de servidores

7. 4 Gwengolo 2026 da 20:41 UTCresolved

   Este incidente foi resolvido e as filas de e- mail voltaram ao normal. Obrigado pela vossa paciência.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Eost 2026 da 22:38 UTCidentified

   Identificamos o problema que faz com que alguns clientes sintam problemas de conexão e atrasos de entrega (com e-mails permanecendo no estado "Processado"). Nossa equipe está trabalhando com urgência para resolver o problema e restaurar o serviço normal.

2. 27 Eost 2026 da 23:01 UTCmonitoring

   Foi implementada uma correção e continuamos a monitorar os resultados. A estabilidade da conexão está melhorando, os níveis de fila estão caindo, e emails atrasados estão sendo processados.

3. 27 Eost 2026 da 23:21 UTCmonitoring

   Continuamos a acompanhar a situação. Se você ainda estiver tendo problemas de conexão ou atrasos de entrega, por favor, contate nossa equipe de suporte para obter ajuda.

4. 27 Eost 2026 da 23:44 UTCresolved

   Este incidente foi resolvido. Pedimos sinceramente desculpas pela perturbação e inconveniência causada. Se você tiver quaisquer problemas adicionais com conexão ou entrega de e-mail, por favor, contate nossa equipe de suporte para obter assistência.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Eost 2026 da 03:20 UTCinvestigating

   Nossa equipe está atualmente investigando um problema que faz com que alguns e-mails permaneçam no estado "Processado", resultando em atrasos na entrega. Estamos a trabalhar para resolver a questão.

2. 27 Eost 2026 da 03:57 UTCinvestigating

   Continuamos a investigar esta questão.

3. 27 Eost 2026 da 04:52 UTCmonitoring

   Foi implementada uma solução e estamos a acompanhar os resultados. O backlog de e-mails mantidos no estado "Processado" agora está sendo trabalhado.

4. 27 Eost 2026 da 05:18 UTCmonitoring

   Continuamos a monitorizar.

5. 27 Eost 2026 da 06:40 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Eost 2026 da 16:47 UTCinvestigating

   Os utilizadores europeus podem ter um atraso no estado de entrega a ser actualizado no painel. Nossos desenvolvedores estão atualmente trabalhando em uma correção. Tenha certeza de que os e-mails foram entregues com sucesso, apesar das atualizações de status atrasadas.

2. 19 Eost 2026 da 06:01 UTCresolved

   Este incidente foi resolvido. Se você ainda tiver e-mails mostrando apenas como "Processado", por favor, contate nossa equipe de suporte que pode ajudar ainda mais.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Gouere 2026 da 19:01 UTCinvestigating

   Nossos desenvolvedores estão investigando um problema causando atrasos no processamento de email. Alguns usuários no servidor afetado podem ver e-mails estranhos presos no palco "Processado" em sua página de Atividade, enquanto outros estão sendo entregues.

2. 26 Gouere 2026 da 06:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 09:42 UTCinvestigating

   We are currently investigating an issue with email delivery

2. 1 Gouere 2026 da 10:01 UTCmonitoring

   The issue has been identified and addressed

3. 1 Gouere 2026 da 10:10 UTCresolved

   This incident has been resolved.

1. 25 Mezheven 2026 da 10:32 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. 25 Mezheven 2026 da 12:20 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. 25 Mezheven 2026 da 17:27 UTCmonitoring

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

4. 25 Mezheven 2026 da 17:27 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25 Mezheven 2026 da 18:29 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. 1 Mezheven 2026 da 07:31 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. 1 Mezheven 2026 da 08:48 UTCinvestigating

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

3. 1 Mezheven 2026 da 09:18 UTCidentified

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

4. 1 Mezheven 2026 da 09:40 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. 1 Mezheven 2026 da 09:41 UTCmonitoring

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

6. 1 Mezheven 2026 da 10:35 UTCresolved

   This incident has been resolved.

1. 4 Mae 2026 da 19:04 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. 4 Mae 2026 da 22:29 UTCresolved

   This incident has been resolved.

1. 30 Ebrel 2026 da 06:25 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. 30 Ebrel 2026 da 08:35 UTCresolved

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

1. 30 Ebrel 2026 da 03:35 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. 30 Ebrel 2026 da 04:00 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. 30 Ebrel 2026 da 05:17 UTCresolved

   This incident has been resolved.

1. 15 Ebrel 2026 da 16:26 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. 15 Ebrel 2026 da 17:23 UTCresolved

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

1. 31 Meurzh 2026 da 23:08 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. 31 Meurzh 2026 da 23:58 UTCidentified

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

3. 1 Ebrel 2026 da 02:09 UTCidentified

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

4. 1 Ebrel 2026 da 05:28 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. 1 Ebrel 2026 da 09:53 UTCresolved

   This incident has been resolved.

1. 2 Meurzh 2026 da 17:00 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. 2 Meurzh 2026 da 22:36 UTCmonitoring

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

3. 3 Meurzh 2026 da 00:08 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. 26 Cʼhwevrer 2026 da 03:01 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. 27 Cʼhwevrer 2026 da 03:08 UTCresolved

   This incident has been resolved.

1. 13 Cʼhwevrer 2026 da 14:36 UTCidentified

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

2. 14 Cʼhwevrer 2026 da 04:10 UTCresolved

   This incident has been resolved.

1. 8 Cʼhwevrer 2026 da 23:57 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. 9 Cʼhwevrer 2026 da 02:51 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. 22 Genver 2026 da 19:44 UTCinvestigating

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

2. 22 Genver 2026 da 20:02 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. 24 Genver 2026 da 00:26 UTCresolved

   This incident has been resolved.

1. 20 Genver 2026 da 15:27 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. 20 Genver 2026 da 16:08 UTCinvestigating

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

3. 21 Genver 2026 da 03:57 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. 12 Genver 2026 da 15:33 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. 12 Genver 2026 da 18:11 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.