cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This page is no longer active

close

   

For up-to-date information and comments, search the EE Community or start a new topic.

Recent network work at xxx xxx mast seems to have affected HTTPs traffic

simona67
Investigator
Investigator

Hi

 

You recently carried out work on the 4G mast at xxx xxx. The 4G was down for about 3-4 hours during that day and your website status said that engineers were upgrading the site. (I'm sorry, I didn't make a note of the date, but it was early-mid January 2021).

 

Before the upgrade my 4GEE Internet was perfect, couldn't fault it. I use a 4GEE router, and yes, I have rebooted it to make sure it was not an issue with that.

 

Since the upgrade I am now seeing many problems with HTTPs traffic, which result in the web browser stalling 'Perfoming a TLS handshake' for sometimes up to 30 seconds or more, or even failing to make that connection completely. This happens with different browsers (Firefox, Chrome, Edge etc) and on different PCs running different OS's (Win 10 and Linux). It seems to be for sites that make lots of connections (e.g. a site with maps that load many map tiles from the same server, or perhaps a shopping site showing lots of images etc) so I wonder if there is some kind of connection limit now for TLS connections?

 

Anyway, *something* has changed on your network since the 'upgrade' work was carried out near me.

 

Please can you look in to this or ask an engineer that carried out this work if they can see a correlation between the work done and the issue I am describing.

1 REPLY 1
bristolian
EE Community Star
EE Community Star

Hi @simona67 

 

There is no formal fault reporting via this public forum, for coverage related issues you can use the coverage & status checker and select "I have a problem".

 

That said, the issues you describe are not symptomatic of a coverage issue - they're a routing issue, which is managed at core/central network level. If this is indeed such an issue, it would affect all the network sites across a wider area.

 

The best way to report core/central network issues such as this is to call C/S (on 150) and speak to a second-line tech agent who have access to more advanced toolsets.