Not connecting

matday

I didn't even think to check, its 'never' down..... ;-)

I'm back online now :-)

FleetSupport

Hi @Esther 

we are glade to report that TeamViewer 14 is now up and running from our side in South Africa.

again thanks for the support and keeping us up to date.

Hi @Philipppp 

thanks for reporting the issue with and to all the support for everyone.

 

Bjorgvin

I can confirm that this works! Just tried on 2 of our laptops we hadn't fixed. Fantastic job guy's and gals :-)

 

Cheers, Björgvin

ZGralewski

Exactly. I thought my dns crashed, then called internet provider just to be sure :P Last thing to check is if TV is down )) Well.... good job gettin us back online Teaviewer Team is the best!

JPD

Thank you Esther. Clients are now working here in the UK with "Automatically Detect Settings" enabled.

larsoh

Thanks for solving the issue!

May I suggest giving the client an extra way of checking internet access (pinging some known DNS for instance), to avoid blaming not reaching your unresponsive servers on lack of internet access?

ZGralewski

I have stumbled many times on the situation when different SSL based services/programs stop working or stop connecting. Many times restarting (switching off then on) SSL/TLS protocol filtering in ESET was sufficient. Probably there was something with certificate installation and using this reinstalls the certificates and things start to work again.

So, restart SSL/TLS filtering if things stop working.

Esther

Hi all,

Thank you once again for your patience and understanding related to today´s connectivity issues with TeamViewer service.

I was talking to the engineering team about it and wanted to summarize this for you to keep you updated:

• While we witnessed a brief hitch on some parts of our network yesterday, it was swiftly dealt with by our engineering team. We were facing the same problem earlier today.
• Today’s issue did not affect existing connections and sessions
• Our engineers were able to identify the root cause within about 30 minutes, and they were ready to start working on a fix.
• The performance picked up after a while for some of our users, and the full availability was restored about 3 hours after the issue occurred.
• The root cause of the issue is under investigation. Now that the incident has been solved, the responsible teams will continue with the root cause analysis. The main focus during the incident was to ensure that the expected service quality is restored and to make TeamViewer accessible for all clients.

We apologize for any inconvenience that you may have encountered during this time. I can assure you that our engineers have worked diligently to ensure that performance is fully restored and thanks to their thorough efforts, the issue has been fully resolved.

We continue to work continuously to provide our customers and free users with efficient and reliable software. The whole team spares no effort to make sure that our software runs smoothly and stably for all of you!

Thanks again for your patience and thanks for using the TeamViewer Community to get up-to-date information and for getting in contact with us.

Best regards,
Esther

Esther

Hi @larsoh 

Thanks for your suggestion.

You can always try to ping master1.teamviewer.com till master16.teamviewer.com.

I hope this info helps you.

Best, Esther

Esther

Hi all,

As this thread discussed the connectivity issue from April 11th, 2019, I am going ahead and close this thread.

Thanks!

Esther