Is anyone else occasionally getting a 'connection down' error from Chrome (or 'Secure Connection Failed' from Firefox) when changing page - if I hit refresh it works fine. At first I wondered if it was the site I was using but have noticed it on multiple different major websites over the past couple of months and not noticed it from other locations where I don't use Three Broadband so does seem to be related to the router/connection (this is via wired Ethernet too, so not a WiFi problem). I've tried changing DNS server in case that helps but no difference.
It mainly seems to happen when trying to first load a site or (annoyingly) at checkout when a different site is being loaded as part of the checkout process. It certainly doesn't happen everytime but does happen with reasonable frequency. I've also noticed I often get it when trying to pull/push from/to Github too and have to do so a number of times for it to work (browsing the Github website works fine).
Failed to load their own f'in website..
With visualstudio.microsoft.com, the failure rate is almost 1 in 5 attempts, which is terrible..
Three needs to fix this ASAP..
Another failure, this time at visualstudio.microsoft.com.. Once again, served from Akamai..
Just had it happen again.. This time on sky.com.
Now there is an interesting coincidence here..
The IP address for inews (2.19.176.162) and the one for sky (23.57.166.79) are both served from an Akamai data centre.
Does that mean that Three's network doesn't play nicely with Akamai's infrastructure?
Sadly it was just coincidence.. After spam loading a bunch of pages I started getting some failures again.
Whats interesting is there doesn't seem to be any suitable explanation for it from the wireshark logs..
Here's a side-by-side of a connection to inews, one fails and one works.
The first picture shows the log from the failed attempt. The curious part of this is that at *exactly* the same time as the 'window update', a FIN is sent from the server to close the connection.
Compare this to refreshing the page, which loads correctly
The opening sequence is identical... Except that WireShark identifies the working session 'Hello' as TLS v1.3, where as the failed session it identified as TLS v1. I suspect this is a identification discrepancy with wireshark. The details both show the same version IDs.
Not sure from here, if anyone has any more insight on this I can provide these two sessions as wireshark files.
The oddity for me is the FIN coming in, initiated by the server end.
