Hacker News Reader

Comment by colordrops | Hacker News Reader

I regularly get 12ms latency to google over my DOCSIS3 cable coax connection.

This will vary greatly depending on how loaded your particular cablemodem segment is, how the channel bonding is set up, how enthusiastic your neighbors are about downloading things like 65GB torrents of 2160p60 movies. If there is an 8.8.8.8 anycast node somewhere in your city, and you are kinda close to downtown, less than 1.5ms of that could be the fiber path from your ISP to their peering with google and back, and 10.5ms of it or so would be accounted for by the cablemodem part.

It will also vary greatly once starlink is loaded. The variation you're seeing is purely due to slant range. Those numbers will increase once the satellites are oversubscribed.

Very true. I'm seeing an average of 100ms to the first hop (and about the same to 8.8.8.8) during the day on mine, with lows of 50-60ms, and the occasional 10 second peaks.

At night it's something like 10ms.

I regularly get 25-250ms latency (average is maybe 60ms) to google or 8.8.8.8 over my DOCSIS3 cable coax connection in addition to 2-5% packet loss.

The ISP network and node is oversaturated and they plan to do nothing about it (Cox).

So I'm actually excited if Starlink can provide 20-30ms stable latency, I have an option which is not tied to the regional operators.

Latency or RTT?

I just checked mine. I get about the same.

Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=12ms TTL=115

8.8.8.8 is 13ms , but how does Cloudfare (1.1.1.1) get to 1ms ?

Reply from 1.1.1.1: bytes=32 time<1ms TTL=60

Some sort of local caching going on.

Whoa, do you live in their data center? ;-)

Even my ISP's next hop is 2.5ms, 8.8.8.8 and 1.1.1.1 are both at 4.7ms.

Google probably have servers in your ISPs data center

Yes, this. I know they do with Videotron.

Reply on news.ycombinator.com