Smtp2go driftsforstyrrelser

1. 4. september 2026 kl. 08.58 UTCinvestigating

   Vores team undersøger i øjeblikket et problem, der forårsager nogle e-mails til at forblive i "Forarbejdede" tilstand til Microsoft e-mail-adresser, hvilket resulterer i levering forsinkelser og greylisting. Vi arbejder på at løse problemet. Vi anbefaler safelisting hvor som helst det er muligt: https: / / support.smtp2go.com / hc / en- gb / artikler / 3600471954-Allowing- IP- Respects- Wit- Microsoft- 365

2. 4. september 2026 kl. 11.17 UTCidentified

   Mens vi fortsætter med at håndtere det igangværende problem med Microsoft-domæner, alle indikatorer peger på et større, globalt problem med Microsoft selv. Vi vil fortsætte med at levere opdateringer, som de er tilgængelige. https: / / groups.io / email- provider- status? isp = Microsoft + 365

3. 4. september 2026 kl. 12.04 UTCidentified

   Microsoft har accepteret ansvaret for de aktuelle e-mail forsinkelser. Flere detaljer kan findes på deres status side og nedenfor: Udstedelse: EX1467029 Berørte tjenester: Exchange Online Status: Forringelse af tjenesten Udstedelsestype: hændelse Starttid: 4 sep, 2026, 10: 19 PM GMT + 12 Brugereffekt Brugere kan opleve en forsinkelse i at sende og modtage e-mails fra eksterne domæner i Exchange Online. Mere info Brugere kan opleve intermitterende "Server travle" fejl, der påvirker flere postkasser. Påvirkningens omfang Dette problem påvirker brugere, der kan forsøge at sende og modtage e-mails fra eksterne domæner i Exchange Online. Disse oplysninger kan opdateres, efterhånden som vores undersøgelse fortsætter.

4. 4. september 2026 kl. 14.04 UTCidentified

   Vi undersøger, da dette spørgsmål nu er begyndt at påvirke andre udbydere, såsom Gmail

5. 4. september 2026 kl. 14.26 UTCinvestigating

   Vores tekniske team undersøger et problem med nogle beskeder til forskellige udbydere bliver vist som "Forarbejdede" og ikke når modtageren

6. 4. september 2026 kl. 14.38 UTCmonitoring

   Overskydende serverbyrde forårsaget af banke på effekter fra Microsoft service-problemet forårsaget unormale udgående køer. Et fix er blevet implementeret, og vi overvåger serverkøer

7. 4. september 2026 kl. 20.41 UTCresolved

   Denne hændelse er blevet løst og mail køer er vendt tilbage til normal. Tak for din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 22.38 UTCidentified

   Vi har identificeret problemet, der får nogle kunder til at opleve forbindelse problemer og leveringsforsinkelser (med e-mails tilbage i "Forarbejdede" tilstand). Vores team arbejder hurtigt på at løse problemet og genoprette normal service.

2. 27. august 2026 kl. 23.01 UTCmonitoring

   Der er gennemført et fix, og vi overvåger fortsat resultaterne. Forbindelsesstabiliteten forbedres, køniveauet falder, og forsinkede e-mails behandles.

3. 27. august 2026 kl. 23.21 UTCmonitoring

   Vi følger fortsat situationen. Hvis du stadig oplever problemer med forbindelse eller leveringsforsinkelser, bedes du kontakte vores support team for at få hjælp.

4. 27. august 2026 kl. 23.44 UTCresolved

   Denne hændelse er blevet løst. Vi undskylder virkelig for de forstyrrelser og ulemper, der er forårsaget. Hvis du oplever yderligere problemer med forbindelse eller e-mail levering, bedes du kontakte vores support team for hjælp.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 03.20 UTCinvestigating

   Vores team er i øjeblikket ved at undersøge et problem forårsager nogle e-mails til at forblive i "Forarbejdede" tilstand, hvilket resulterer i levering forsinkelser. Vi arbejder på at løse problemet.

2. 27. august 2026 kl. 03.57 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 27. august 2026 kl. 04.52 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne. Den manglende e-mail i den "Forarbejdede" tilstand er nu under behandling.

4. 27. august 2026 kl. 05.18 UTCmonitoring

   Vi fortsætter med at overvåge.

5. 27. august 2026 kl. 06.40 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. august 2026 kl. 16.47 UTCinvestigating

   Europæiske brugere kan opleve en forsinkelse i leveringsstatus, der opdateres i instrumentbrættet. Vores udviklere arbejder i øjeblikket på et fix. Vær sikker på, at e-mails er blevet leveret med succes på trods af de forsinkede statusopdateringer.

2. 19. august 2026 kl. 06.01 UTCresolved

   Denne hændelse er blevet løst. Hvis du stadig har e-mails, der kun viser som "Forarbejdede", bedes du kontakte vores support team, der kan hjælpe yderligere.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. juli 2026 kl. 19.01 UTCinvestigating

   Vores udviklere er ved at undersøge et problem forårsager forsinkelser i e-mail-behandling. Nogle brugere på den berørte server kan se ulige e-mails sidder fast i "Forarbejdede" scenen på deres Aktivitet side, mens andre bliver leveret.

2. 26. juli 2026 kl. 06.00 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 09.42 UTCinvestigating

   We are currently investigating an issue with email delivery

2. 1. juli 2026 kl. 10.01 UTCmonitoring

   The issue has been identified and addressed

3. 1. juli 2026 kl. 10.10 UTCresolved

   This incident has been resolved.

1. 25. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 17.27 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 08.48 UTCinvestigating

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

3. 1. juni 2026 kl. 09.18 UTCidentified

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

4. 1. juni 2026 kl. 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. juni 2026 kl. 09.41 UTCmonitoring

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

6. 1. juni 2026 kl. 10.35 UTCresolved

   This incident has been resolved.

1. 4. maj 2026 kl. 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. maj 2026 kl. 22.29 UTCresolved

   This incident has been resolved.

1. 30. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 05.17 UTCresolved

   This incident has been resolved.

1. 15. april 2026 kl. 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. april 2026 kl. 17.23 UTCresolved

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

1. 31. marts 2026 kl. 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. marts 2026 kl. 23.58 UTCidentified

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

3. 1. april 2026 kl. 02.09 UTCidentified

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

4. 1. april 2026 kl. 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. april 2026 kl. 09.53 UTCresolved

   This incident has been resolved.

1. 2. marts 2026 kl. 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. marts 2026 kl. 22.36 UTCmonitoring

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

3. 3. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 03.08 UTCresolved

   This incident has been resolved.

1. 13. februar 2026 kl. 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. februar 2026 kl. 04.10 UTCresolved

   This incident has been resolved.

1. 8. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 00.26 UTCresolved

   This incident has been resolved.

1. 20. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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.