I've just migrated and had a similar blip, which my ISP put down to DLM. I note UKHardy has also suggested it was DLM triggered. The workings of DLM are a bit of a mystery, so I for one are unable to explain it further.

The good news from your stats is that (as you have already spotted) there is no interleaving on your line, although your Errored Seconds count is a bit higher than ideal.

I'd certainly be having words with TT about why your speed test results are as low as they are.

Sorry for the false alarm. I just realised that my SQM (Smart Queue Management) QoS settings on my WRT1900ACS (with LEDE OpenWRT) were still ones leftover from the Virginmedia cable connection. There are significant differences especially when it comes to Link Layer Adaptation settings, which I have now corrected.

The speed looks normal now! (even over WiFi)


With corrected SQM QoS settings: https://www.thinkbroadband.com/speedtest/15168015122...

With SQM QoS Disabled: https://www.thinkbroadband.com/speedtest/15168018476...

Thanks everyone.

In any case, do my line stats still look okay?

BQM is looking better, now to see how it stands up what ever is peak time in your place

Yes! Still monitoring the connection here. Do you (or anyone here) knows by any chance what protocol TalkTalk is using exactly?

It's definitely not PPPoE or PPPoA. In DrayTek configurations, I had to use MPoA/Dynamic IP to get a sync. Any idea what does this mean or how does it work?

Thanks

In reply to a post by nidstigator:

Do you (or anyone here) knows by any chance what protocol TalkTalk is using exactly?

They use DHCP, routers seem to call it Dynamic IP or IPoE.

Hi guys,

I recently joined talktalk myself.
Currently facing extremely poor WhatsApp video calls to and from other talktalk fibre connections.. this goes away if use VPN or my mobile data.
Did some tracerts and pings to whatsapp.com and yes pings over 250ms direct and 80ms via VPN. Traceroute showed -4 routes on VPN and less timing too

Is this a talktalk issue with their weird routing, any ideas how to cure it apart from living VPN always on which I don't really want to do as it affects Netflix and prime video in the house..

kannanni -

Have you tried using different DNS's. ?

i.e. anything other than TalkTalk's own.

In reply to a post by kannanni:

Hi guys,

I recently joined talktalk myself.
Currently facing extremely poor WhatsApp video calls to and from other talktalk fibre connections.. this goes away if use VPN or my mobile data.
Did some tracerts and pings to whatsapp.com and yes pings over 250ms direct and 80ms via VPN. Traceroute showed -4 routes on VPN and less timing too

Is this a talktalk issue with their weird routing, any ideas how to cure it apart from living VPN always on which I don't really want to do as it affects Netflix and prime video in the house..

I am using Cloudflares DNS and am getting the same results.
https://www.cloudflare.com/learning/dns/what-is-1.1....


Ping results - https://i.postimg.cc/9M6PVw8f/ping.jpg

Added this in case its of use - https://i.postimg.cc/PJfS0wP8/trace.jpg

Edit to add second link.

Edited by deleted (Tue 07-Jan-20 15:58:57)

I use cloudflare and Google DNS too.
This is not related to dns. It's just poor talktalk routing/peering I'm afraid..talktalk support thinks this is normal and cannot fix it. Virgin,bt,hyperoptic I tested today all return 70-80ms to WhatsApp servers.
I resolved using duo for now for video calls and it's better..

Well I joined TalkTalk FTTC 4 days ago and I get very low pings.

C:\Windows\system32>ping whatsapp.com

Pinging whatsapp.com [169.55.60.148] with 32 bytes of data:
Reply from 169.55.60.148: bytes=32 time=77ms TTL=51
Reply from 169.55.60.148: bytes=32 time=77ms TTL=51
Reply from 169.55.60.148: bytes=32 time=76ms TTL=51
Reply from 169.55.60.148: bytes=32 time=77ms TTL=51

Ping statistics for 169.55.60.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 77ms, Average = 76ms

C:\Windows\system32>ping lichess.org

Pinging lichess.org [37.187.205.99] with 32 bytes of data:
Reply from 37.187.205.99: bytes=32 time=6ms TTL=54
Reply from 37.187.205.99: bytes=32 time=6ms TTL=54
Reply from 37.187.205.99: bytes=32 time=6ms TTL=54
Reply from 37.187.205.99: bytes=32 time=7ms TTL=54

Ping statistics for 37.187.205.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms

C:\Windows\system32>ping bbc.com

Pinging bbc.com [151.101.64.81] with 32 bytes of data:
Reply from 151.101.64.81: bytes=32 time=4ms TTL=59
Reply from 151.101.64.81: bytes=32 time=3ms TTL=59
Reply from 151.101.64.81: bytes=32 time=3ms TTL=59
Reply from 151.101.64.81: bytes=32 time=4ms TTL=59

Ping statistics for 151.101.64.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4ms, Average = 3ms

Generally speaking 3-6ms ping across all of these tests. In speed tests I also get 4-5ms ping consistently here in London, Bishopsgate.

I think latency may be area specific. This is the first time I've had pings this low. With ADSL Plusnet was 20ms and with Sky it was 12ms. Lichess.org I was getting 24ms ping with Sky/Plusnet ADSL. But with TalkTalk FTTC so far it has been 6ms ping which is a massive difference.