I too have had a few hiccoughs over recent days. It's really hard to tell because they're so random.

Weird event at 7:54 am when the router reconnected—to a cell whose beam is pointing in the opposite direction, then reconnected again to the correct cell, 45 seconds later. Almost as if they're reconfiguring the gear again.

PMTU to well-known sites still 1400.

I've also experienced some hiccups as well - two evenings in a row the download speed went from c280Mbps down to being so slow that FaceTime video dropped out. Last night the download speed was between 6 and 20Mbps for an hour or so.

I've also noticed that slow page loads have come back again - it's intermittent but still enough that I'll likely cancel my Three subscription in the next month or so. Ultimately if Three can't even maintain good network performance on their newly upgraded 5G sites it's probably only going to get worse as more 5G devices are used.

In reply to a post by richi:

Weird event at 7:54 am when the router reconnected—to a cell whose beam is pointing in the opposite direction, then reconnected again to the correct cell, 45 seconds later. Almost as if they're reconfiguring the gear again.

Eight hours on and I've had no problems loading any sites.

Still bad today. I can replicate from the command line ...

If I repeatedly open SSL connections, I eventually get this:-

openssl s_client -servername forums.thinkbroadband.com -connect forums.thinkbroadband.com:443
CONNECTED(00000003)

A tcpdump shows the connection has been established and the initial TLS request from me to website acknowledged by the far end at a tcp level but then no further traffic gets passed. It then times out.

I wonder if this someone to do with Three content filter? When I started my contract 2 weeks ago, there was no content filtering and then a few days days ago it started filtering the "adult" sites so I contacted them and got them to turn it off. Since then the stalling issue has returned.

I've taken a few more tcpdumps of various sites. They all behave the same...

1) 3 way handshake works fine
2) client sends Hello, far end ACKs the tcp packet
3) <no more ssl traffic>
4) far end sends FIN exactly 127 seconds later

This is the exact same story for many websites that I've tested. Akamai, Cloudflare,etc all the same. They are unlikely to behave in exactly the same way unless there's something in between us and them that's the common factor - e.g. a transparent filtering proxy

In reply to a post by Appy:

e.g. a transparent filtering proxy

Always possible, and I think Smarty uses one, we didn't think Three used one.

I can provoke a hung SSL connection to news.tweaknews.eu on port 443 but I can't provoke it on port 563 using the same method to the same server, and almost certainly the same application, just different ports. There's got to be something in between filtering traffic.

news.tweaknews.eu seems to be down

https://downforeveryoneorjustme.com/news.tweaknews.eu

But tweaknews.eu works fine for me. (On Three).

Edit: Actually https://tweaknews.eu

Edited by RobertoS (Wed 23-Sep-20 19:16:23)

It's up and running, but it's an nntp service not a website

Post deleted by RobertoS