Logmein Rescue driftsforstyrrelser

1. 4. september 2026 kl. 12.31 UTCinvestigating

   Vi undersøger aktivt rapporter om, at nogle kunder kan opleve problemer i at modtage e-mails fra GoTo, især herunder 2FA bekræftelser for Resolve, Rescue og GoToMyPC. Vores ingeniører arbejder på at identificere problemet og vil give en anden opdatering snart.

2. 4. september 2026 kl. 12.47 UTCidentified

   Vores ingeniører har identificeret den e-mail levering sats er forbedret og arbejder løbende mod en løsning med vores mail levering partner. Vi vil give endnu en opdatering om kort tid.

3. 4. september 2026 kl. 12.59 UTCmonitoring

   Vores partner har rettet problemet, og vi ser vedvarende stabilitet i e-mail-tjenester. Vi vil fortsat overvåge situationen og fremlægge en endelig opdatering om kort tid.

4. 4. september 2026 kl. 13.31 UTCresolved

   Vi har bekræftet, at problemet er løst, og at alle systemer er 100% operationelle. Vi vil foretage en intern gennemgang af dette spørgsmål og foretage passende forbedringer af vores system for at hjælpe med at forhindre eller minimere fremtidige tilbagefald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 15.55 UTCidentified

   Vores ingeniører er ved at undersøge problemer med kode signering til Rescue, GoToAssist v5, Pro og Central, som kan føre til intermitterende svigt, når du starter sessioner. Vi vil give endnu en opdatering om kort tid.

2. 27. august 2026 kl. 16.38 UTCidentified

   Vores ingeniører fortsætter med at undersøge kode signering spørgsmål rapporteret til Rescue, GoTo Assist v5, Pro, og Central. Vi vil give endnu en opdatering om kort tid.

3. 27. august 2026 kl. 17.40 UTCmonitoring

   Vores ingeniører ser en forbedring af situationen, og vi bekræfter, at alle tjenester er funktionelle. Vi vil fortsat overvåge situationen og fremlægge en endelig opdatering om kort tid.

4. 28. august 2026 kl. 16.24 UTCresolved

   Vi har bekræftet, at problemet er løst, og at alle systemer er 100% operationelle. Vi vil foretage en intern gennemgang af dette spørgsmål og foretage passende forbedringer af vores system for at hjælpe med at forhindre eller minimere fremtidige tilbagefald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. august 2026 kl. 15.02 UTCidentified

   Vores ingeniører er klar over et problem, der påvirker password reset og OTP e-mails påvirker Microsoft365 og Outlook-brugere. Vi har identificeret problemet som et spørgsmål om leverandør, og vi har samarbejdet med dem om at arbejde hen imod en løsning. Vi vil give endnu en opdatering om kort tid.

2. 15. august 2026 kl. 15.52 UTCmonitoring

   Vores ingeniører er begyndt at se tegn på helbredelse efter en intern afbødning, som de fortsætter med at engagere sælgeren til endelig løsning. Vi ser, at reles er en succes, sådan at berørte brugere har været i stand til at modtage password og autentificering trafik. Vi vil fortsat overvåge situationen og fremlægge en endelig opdatering om kort tid.

3. 15. august 2026 kl. 16.33 UTCresolved

   Vi har bekræftet, at problemet er løst, og at alle systemer er 100% operationelle. Vi vil foretage en intern gennemgang af dette spørgsmål og foretage passende forbedringer af vores system for at hjælpe med at forhindre eller minimere fremtidige tilbagefald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 4. august 2026 kl. 18.11 UTCidentified

   Our team is working on an issue regarding WhatsApp campaigns. Until this is resolved, we have temporarily disabled the following features and added an in-app notification for the affected customers. - Customers cannot send campaigns or initiate outbound conversations - Customers cannot onboard new WhatsApp numbers SMS campaigns are unaffected by this and remain functional. We are working with Meta to resolve this situation and will post an update as soon as possible.

2. 7. august 2026 kl. 19.44 UTCidentified

   We are still fully engaged in the incident's resolution and are escalating the matter with Meta on all means available. We will post another update as soon as the situation progresses.

3. 13. august 2026 kl. 17.48 UTCidentified

   Our engineers have made progress on the escalation with Meta and we are working to re-enable the Whatsapp 1-to-1 template features for all affected customers. WhatsApp campaigns are being addressed separately and remain unavailable for now. We will update this page as soon as we have a restoration estimate for this feature.

4. 14. august 2026 kl. 15.11 UTCmonitoring

   Following the re-enablement of 1-to-1 templates yesterday, our engineers have re-enabled WhatAapp campaigns for all affected customers. A reload of the GoTo App will be necessary to access this feature again.

5. 14. august 2026 kl. 16.09 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 3. juli 2026 kl. 12.03 UTCinvestigating

   Vi undersøger aktivt rapporter om, at nogle Pro og Central kunder kan opleve problemer, når de forsøger at logge ind. Vores ingeniører arbejder på at identificere problemet og vil give en anden opdatering snart.

2. 3. juli 2026 kl. 12.39 UTCinvestigating

   Vores ingeniører arbejder stadig på at identificere kilden til dette problem og vil give endnu en opdatering om kort tid.

3. 3. juli 2026 kl. 13.23 UTCidentified

   Vores ingeniører har identificeret problemet og arbejder nu aktivt hen imod en resolution. Vi vil give endnu en opdatering om kort tid.

4. 3. juli 2026 kl. 14.05 UTCidentified

   Vores ingeniører har udført en ændring, som vil hjælpe genoprette funktionalitet. Det kan dog tage op til 4 timer at få fuld virkning. I mellemtiden kan login være periodisk arbejde. Holdet ser også på andre muligheder for at komme til en hurtigere genopretning. Vi vil give endnu en opdatering om kort tid.

5. 3. juli 2026 kl. 15.08 UTCidentified

   Vores ingeniører har udført en ændring for at genoprette funktionalitet. Det er stadig i gang med fuld virkning. I mellemtiden kan login være periodisk arbejde. Holdet er også stadig ser på andre muligheder for at komme til en hurtigere genopretning. Vi vil give en anden opdatering, når nye oplysninger er tilgængelige.

6. 3. juli 2026 kl. 16.02 UTCidentified

   Vores ingeniører følger nøje forandringens udvikling i retning af opløsning og undersøger en hurtigere løsning. Login kan stadig fungere periodisk. Vi vil snart give endnu en opdatering.

7. 3. juli 2026 kl. 18.21 UTCidentified

   Vores ingeniører har identificeret, at ændringer ikke gav det forventede resultat og arbejder nu på en alternativ løsning. Vi vil give endnu en opdatering om kort tid.

8. 3. juli 2026 kl. 19.21 UTCidentified

   Vores ingeniører ser tegn på forbedringer for Join.me, Pro og Central og arbejder stadig på opløsning for GoToMyPC. Vi vil give endnu en opdatering om kort tid.

9. 3. juli 2026 kl. 19.55 UTCmonitoring

   Vores ingeniører har rettet op på problemet, og vi bekræfter, at alle tjenester er funktionelle. Vi vil fortsætte med at overvåge situationen og levere en endelig opdatering.

10. 3. juli 2026 kl. 20.25 UTCresolved

    Vi har bekræftet, at problemet er løst, og at alle systemer er 100% operationelle. Vi vil foretage en intern gennemgang af dette spørgsmål og foretage passende forbedringer af vores system for at hjælpe med at forhindre eller minimere fremtidige tilbagefald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 11.49 UTCinvestigating

   Vi undersøger aktivt rapporter om, at en delmængde af GoTo Connect kunder kan opleve problemer med indgående og udgående opkald. Vores ingeniører arbejder på at identificere problemet og vil give en anden opdatering snart.

2. 2. juli 2026 kl. 11.54 UTCidentified

   Vores ingeniører har identificeret problemet og arbejder nu aktivt hen imod en resolution. Vi vil give endnu en opdatering om kort tid.

3. 2. juli 2026 kl. 13.43 UTCidentified

   Vores ingeniører fortsætter med at undersøge problemet og arbejder aktivt på at bestemme den bedste vej mod løsning. Vi vil give endnu en opdatering om kort tid.

4. 2. juli 2026 kl. 14.12 UTCidentified

   Vores ingeniører arbejder i øjeblikket på en plan for at afbøde problemerne og fortsætte med at arbejde hen imod løsning. Vi vil give endnu en opdatering om kort tid.

5. 2. juli 2026 kl. 15.14 UTCidentified

   Vores ingeniører fortsætter med at implementere et fix for problemet. Vi vil give endnu en opdatering om kort tid.

6. 2. juli 2026 kl. 16.06 UTCidentified

   Vores ingeniører fortsætter med at undersøge flere underliggende årsager, der resulterer i det kendte problem. Dette omfatter identifikation og følgende mønstre, samt forståelse af den fulde kundeeffekt er. På nuværende tidspunkt er undersøgelsen i gang. Vi vil levere yderligere opdateringer om kort tid.

7. 2. juli 2026 kl. 16.36 UTCmonitoring

   Vores ingeniører har implementeret en rettelse, der har behandlet indgående / udgående opkald spørgsmål, der blev rapporteret, og vi er nu overvåger for fortsat stabilitet. Vi vil levere en endelig opdatering om kort tid.

8. 2. juli 2026 kl. 18.27 UTCresolved

   Vores ingeniører ser nu, at alle tjenester er funktionelle. Vi vil foretage en intern gennemgang af dette spørgsmål og vil foretage passende forbedringer for at sikre, at dette spørgsmål ikke gentager sig.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 09.43 UTCinvestigating

   Vi undersøger aktivt rapporter om, at en delmængde af GoTo Connect kunder kan opleve problemer med indgående og udgående opkald. Vores ingeniører arbejder på at identificere problemet og vil give en anden opdatering snart.

2. 1. juli 2026 kl. 10.08 UTCidentified

   Vores ingeniører har identificeret problemet og arbejder nu aktivt hen imod en resolution. Vi vil give endnu en opdatering om kort tid.

3. 1. juli 2026 kl. 10.40 UTCmonitoring

   Vores ingeniører har rettet op på problemet, og vi bekræfter, at alle tjenester er funktionelle. Vi vil fortsat overvåge situationen og fremlægge en endelig opdatering inden længe.

4. 1. juli 2026 kl. 10.43 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 1. juli 2026 kl. 10.50 UTCresolved

   Vi har bekræftet, at problemet er løst, og at alle systemer er 100% operationelle. Vi vil foretage en intern gennemgang af dette spørgsmål og foretage passende forbedringer af vores system for at hjælpe med at forhindre eller minimere fremtidige tilbagefald.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. juni 2026 kl. 08.33 UTCinvestigating

   We are actively investigating reports of an impact affecting GoTo Connect, including Call History, Virtual Receptionist Reporting, Voicemail Deletion, and Call-Report Ingestion. Our engineers are working to identify the issue and will provide another update shortly.

2. 19. juni 2026 kl. 08.38 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 19. juni 2026 kl. 10.08 UTCidentified

   Our engineers continue to investigate the issue. We will provide another update as soon as it is available.

4. 19. juni 2026 kl. 12.39 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

5. 19. juni 2026 kl. 13.11 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 28. maj 2026 kl. 14.17 UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing authentication issues accessing the GoTo app or GoTo Admin or Analytics portals. Our engineers are working to identify the issue and will provide another update shortly.

2. 28. maj 2026 kl. 14.28 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 28. maj 2026 kl. 14.49 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 28. maj 2026 kl. 14.57 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 27. maj 2026 kl. 15.17 UTCinvestigating

   We are actively investigating an issue with Logmein Rescue may have issues starting or joining remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 27. maj 2026 kl. 15.45 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We are seeing gradual improvement and continuing to monitor the progress. We will provide another update shortly.

3. 27. maj 2026 kl. 15.48 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 27. maj 2026 kl. 15.57 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 13. maj 2026 kl. 18.58 UTCinvestigating

   We are actively investigating reports that some LogMeIn Rescue and Central customers may be experiencing issues downloading the applet to start or join remote sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 13. maj 2026 kl. 19.22 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 13. maj 2026 kl. 20.04 UTCidentified

   Our engineers are continuing to work on this issue and continue to work towards a resolution. We will provide another update shortly.

4. 13. maj 2026 kl. 21.13 UTCidentified

   Our engineers are continuing to work on isolating the source of this issue. Due to its intermittent nature, trying again can allow to establish a proper connection. We will provide another update shortly.

5. 13. maj 2026 kl. 22.28 UTCmonitoring

   A potential fix was applied to resolve the issue, and we are continuing to monitor for stability. We will continue monitoring the situation and provide a final update shortly.

6. 13. maj 2026 kl. 22.40 UTCidentified

   Our engineers are still seeing some intermittent issues after the fix and are continuing to investigate those. We will provide a status update once we have further information. We will provide another update shortly.

7. 14. maj 2026 kl. 00.37 UTCidentified

   We are continuing to work towards a resolution to ensure stability in starting and joining sessions. We will provide another update shortly.

8. 14. maj 2026 kl. 01.12 UTCidentified

   Our engineers have identified a plan to get back the system to stustained stability and are starting to execute on it. We will provide another update shortly.

9. 14. maj 2026 kl. 02.03 UTCidentified

   Our engineers are executing on the established plan to get back the system to prolonged stability We will provide another update shortly.

10. 14. maj 2026 kl. 02.12 UTCmonitoring

    Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

11. 14. maj 2026 kl. 02.22 UTCresolved

    We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 8. maj 2026 kl. 01.22 UTCinvestigating

   We are actively investigating reports that some Grasshopper customers may be experiencing login issues on apps. Our engineers are working to identify the issue and will provide another update shortly.

2. 8. maj 2026 kl. 02.09 UTCinvestigating

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 8. maj 2026 kl. 04.10 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 8. maj 2026 kl. 17.11 UTCresolved

   We have confirmed that the issue has been resolved and all systems are 100% operational at this time. We will conduct an internal investigation of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 7. maj 2026 kl. 18.31 UTCidentified

   Our engineers have identified the issue with call recordings and transcripts availability delay and are now actively working towards a resolution. We will provide another update shortly.

2. 8. maj 2026 kl. 01.54 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

3. 8. maj 2026 kl. 02.01 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 6. maj 2026 kl. 16.55 UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issue opening the app. Our engineers are working to identify the issue and will provide another update shortly.

2. 6. maj 2026 kl. 16.57 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 6. maj 2026 kl. 17.06 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 6. maj 2026 kl. 17.23 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 20. april 2026 kl. 14.14 UTCinvestigating

   We are actively investigating reports that some GoTo Meeting and GoTo Admin customers may be experiencing timeouts when performing operations in GoTo Admin and GoTo Meeting components. Our engineers are working to identify the issue and will provide another update shortly.

2. 20. april 2026 kl. 14.34 UTCidentified

   Our engineers have identified the issue and are actively working to correct the underlying cause. This issue appears to have impacted functionality with GoTo Admin, GoTo Connect, Contact Center, Analytics, Resolve, and other related services. We will provide another update shortly.

3. 20. april 2026 kl. 14.55 UTCidentified

   This issue affects authentication to the various GoTo applications, which also affects Resolve, Pro/Central, in addition to GoTo Admin, Connect and Meetings. We will provide another update shortly.

4. 20. april 2026 kl. 15.12 UTCidentified

   Our engineers are seeing signs of recovery for login to our applications. Our team is still engaged in ensuring prolonged stability of the applications. We will provide another update shortly.

5. 20. april 2026 kl. 15.16 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

6. 20. april 2026 kl. 15.23 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 15. april 2026 kl. 21.08 UTCinvestigating

   We are actively investigating reports that some GoTo Connect VoIP Phones Calls customers may be experiencing intermittent issues completing inbound calls. Our engineers are working to identify the issue and will provide another update shortly.

2. 15. april 2026 kl. 21.15 UTCidentified

   Our engineers have identified the issue as being caused by an ongoing incident with one of our underlying third-party service providers who are actively working towards a resolution. We will provide another update as soon as they become available.

3. 15. april 2026 kl. 21.38 UTCmonitoring

   Our underlying third-party service provider has corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 15. april 2026 kl. 21.41 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 6. april 2026 kl. 12.58 UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing issues with call quality for GoToConnect Web, Desktop and Mobile. Our engineers are working to identify the issue and will provide another update shortly.

2. 6. april 2026 kl. 13.16 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 6. april 2026 kl. 13.43 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 6. april 2026 kl. 13.47 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 25. marts 2026 kl. 16.08 UTCinvestigating

   We are actively investigating reports that some GoTo Connect customers may be experiencing audio issues on calls Our engineers are working to identify the issue and will provide another update shortly.

2. 25. marts 2026 kl. 16.15 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 25. marts 2026 kl. 16.20 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

4. 25. marts 2026 kl. 16.35 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.

1. 18. marts 2026 kl. 15.37 UTCinvestigating

   We are actively investigating reports that some GoTo Webinar customers may be experiencing an issue starting sessions. Our engineers are working to identify the issue and will provide another update shortly.

2. 18. marts 2026 kl. 15.51 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

3. 18. marts 2026 kl. 15.58 UTCidentified

   We are seeing improvements in GoTo Webinar, Training and Meeting as mitigating actions are being deployed. We will provide another update shortly.

4. 18. marts 2026 kl. 16.04 UTCmonitoring

   Our engineers have corrected the issue and we are monitoring recovery across all services which were affected. We will continue monitoring the situation and provide a final update shortly.

5. 18. marts 2026 kl. 18.19 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational.

1. 27. februar 2026 kl. 15.52 UTCinvestigating

   We are actively investigating reports that some Contact Center – Call Queue customers may be experiencing issues with queue calls not being distributed to Contact Center agents. Our engineers are working to identify the issue and will provide another update shortly.

2. 27. februar 2026 kl. 17.20 UTCinvestigating

   We are continuing to investigate the reports of call queue distribution issues. Our engineers are still fully engaged to identify the source of issue and will provide another update shortly.

3. 27. februar 2026 kl. 18.00 UTCidentified

   Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.

4. 27. februar 2026 kl. 18.42 UTCmonitoring

   Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

5. 27. februar 2026 kl. 19.15 UTCresolved

   We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.