are you still getting ~80ms with the 169.55.60.148 IP?

I'm getting ~300ms with both the .148 and the original .170

In reply to a post by Myth:

are you still getting ~80ms with the 169.55.60.148 IP?

I'm getting ~300ms with both the .148 and the original .170

You are right, it has gone bonkers again!

Pinging whatsapp.com [169.55.60.170] with 32 bytes of data:
Reply from 169.55.60.170: bytes=32 time=244ms TTL=52
Reply from 169.55.60.170: bytes=32 time=244ms TTL=52
Reply from 169.55.60.170: bytes=32 time=244ms TTL=52
Reply from 169.55.60.170: bytes=32 time=244ms TTL=52

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

C:\Windows\system32>ping 169.55.60.148

Pinging 169.55.60.148 with 32 bytes of data:
Reply from 169.55.60.148: bytes=32 time=225ms TTL=50
Reply from 169.55.60.148: bytes=32 time=225ms TTL=50
Reply from 169.55.60.148: bytes=32 time=225ms TTL=50
Reply from 169.55.60.148: bytes=32 time=225ms TTL=50

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

But this is about the only website that is causing this problem. It was 78ms before but has now jumped to 224ms. Fortunately I don't care about WhatsApp as it doesn't affect me. I care only about a few sites like lichess.org Facebook, Youtube, Steam game server which are all under 6ms. Including Viber.

Ok, something very interesting. Whatsapp.com seemed to have moved servers and is now reporting lower pings!

C:\Windows\system32>ping whatsapp.com

Pinging whatsapp.com [157.240.1.53] with 32 bytes of data:
Reply from 157.240.1.53: bytes=32 time=4ms TTL=55
Reply from 157.240.1.53: bytes=32 time=4ms TTL=55
Reply from 157.240.1.53: bytes=32 time=5ms TTL=55
Reply from 157.240.1.53: bytes=32 time=4ms TTL=55

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

Since yesterday, just out of curiosity I have decided to ping whatsapp, not that I really care about it at all. And it is now pinging at 4-5ms under the new IP address 157.240.1.53. https://whatismyipaddress.com/ip/157.240.1.53 https://ipinfo.io/157.240.1.53

The most bizarre thing is that this new address is still located in the United States. Los Angeles, California.

The old IP address still pings at Ping statistics for 169.55.60.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 233ms, Average = 232ms

https://whatismyip.live/ip/169.55.60.148
So the old IP address for Whatsapp.com that was located in Dallas is pinging at 200+ms. And the same goes with 169.55.60.170

But the new IP address that is under California is pinging at 4-5ms? How comes? I really do not know.

And yes, I am also a TalkTalk FTTC customer.

It is called content delivery networks that mirror popular sites around the globe so you access a version that is closest to you.

You would be changing the laws of physics to get that ping time to the states, it has to be a local site as MrSaffron has explained.

The IP address might show was being in California but with a 4ms response that's certainly not where you're pinging.

Running a tracert to WhatsApp.com ends up with me at whatsapp-cdn-shv-01-ams4.fbcdn.net.

It's there in the hostname, it's a WhatsApp/Facebook CDN and it's based in the UK.

Ok, many thanks, now this makes perfect sense! I too was finding it strange to see it pinging at 4ms initially. I'm aware a ping cannot be that low coming from the US.

Could it be that WhatsApp.com has finally moved to UK servers?

Last 2 months since being a TalkTalk customer, WhatsApp.com has always been mostly 200ms ping with the exception on one occasion when it was 76ms.

Some of the users in this thread were complaining that their pings with WhatsApp.com were too high with TalkTalk something I too have noticed.

Hence why I decided to inform of this new change that I am now seeing with the pings being lower this time around 4-5ms for the first time.

I'm guessing the main concern of having those high pings were that they were contributing to latency delays in video and voice calls? Now with the lower pings the WhatsApp performance should have modest improvements.

You are of course assuming that audio and video is using the whatsapp.com IP address.

An app or webpage can pull/send video/audio to many different places beyond the web page you see in the URL of the page.