Ping to Router vs Ping to Internet - Differences in Latency

[laxboy10]

I have an Asus AC87R with firmware version 3.0.0.4.380_7743 (latest as when I posted). At times my internet becomes extremely slow and I cannot figure the root cause. When I am connected on the 5Ghz band and from a inSSIDer network survey I am the only network transmitting on that channel, the 2.4 Ghz band has others on all channels. The issue occurs on both the 2.4Ghz and 5Ghz bands. When I have tried Merlin firmware in the past and the issue is still present. I have both AiProtect and QoS disabled.

When I ping the router from my pc the response time is 3-5ms with no dropped packets
When I ping Google DNS (8.8.8.8) from my pc the response time 500-2500ms with occasional dropped packets
When I ping Google DNS (8.8.8.8) from the router the response time is 19-22ms with no dropped packets

If I have low latency pinging the router from my pc and the router has low latency pinging the internet, it must be the router that is causing the high latency when pinging from my pc to the internet ... but why and what can be done to fix it?

 

[FreshJR]

Do you have QOS enabled?

 

[laxboy10]

Do you have QOS enabled?

both QOS and AiProtect are disabled

 

[sfx2000]

When I ping Google DNS (8.8.8.8) from my pc the response time 500-2500ms with occasional dropped packets
When I ping Google DNS (8.8.8.8) from the router the response time is 19-22ms with no dropped packets

Don't ping google... it's the cloud, and you're going to get inconsistent results...

 

[Nullity]

Don't ping google... it's the cloud, and you're going to get inconsistent results...

Counter-point: I've been pinging google.com for years and the ping has been incredibly consistent (8-11ms for more than 5 years and always within a millisecond during a given PPPOE/DSLAM session). It's more consistent than any of my ISP's nodes, excluding my first external hop (but that's barely what I would consider the "internet").

 

[RMerlin]

Counter-point: I've been pinging google.com for years and the ping has been incredibly consistent (8-11ms for more than 5 years and always within a millisecond during a given PPPOE/DSLAM session). It's more consistent than any of my ISP's nodes, excluding my first external hop (but that's barely what I would consider the "internet").

Chances are you're actually pinging your ISP (quite a few have nearline Google cache servers on their network), hence it's more stable than any remote site

 

[Nullity]

Chances are you're actually pinging your ISP (quite a few have nearline Google cache servers on their network), hence it's more stable than any remote site

Maybe... I don't understand anycast or low-level tiering very well. The hosts always end up being *.1e100.net, which seems to be Google's network. The traceroute shows the IPs are few hops beyond my ISP's edge.

Also, when I ping my ISP's DNS servers, the results are less consistent along with ~30ms+ pings.

I dunno... *shrug*

 

[RMerlin]

Try a traceroute, you'll see.

In my case, my ISP has great peering with Cloudflare. Here's how it looks like between me and my firmware update server:

merlin@ubuntu-dev:/tmp$ traceroute fwupdate.lostrealm.ca
traceroute to fwupdate.lostrealm.ca (104.27.145.248), 30 hops max, 60 byte packets
 1  Stargate88.lostrealm.lan (192.168.10.1)  3.655 ms  3.272 ms  3.082 ms
 2  * * *
 3  10.170.192.58 (10.170.192.58)  9.633 ms  9.465 ms  9.525 ms
 4  xe-5-2-1-0-bdr01-mtl.teksavvy.com (206.248.155.109)  9.333 ms  9.124 ms xe-0-1-0-0-bdr01-mtl.teksavvy.com (192.171.63.17)  8.957 ms
 5  cloudflare.peer.qix.ca (198.179.18.55)  8.766 ms  8.584 ms  8.412 ms
 6  104.27.145.248 (104.27.145.248)  9.941 ms  10.217 ms  9.721 ms

 

[Nullity]

Try a traceroute, you'll see.

In my case, my ISP has great peering with Cloudflare. Here's how it looks like between me and my firmware update server:

merlin@ubuntu-dev:/tmp$ traceroute fwupdate.lostrealm.ca
traceroute to fwupdate.lostrealm.ca (104.27.145.248), 30 hops max, 60 byte packets
 1  Stargate88.lostrealm.lan (192.168.10.1)  3.655 ms  3.272 ms  3.082 ms
 2  * * *
 3  10.170.192.58 (10.170.192.58)  9.633 ms  9.465 ms  9.525 ms
 4  xe-5-2-1-0-bdr01-mtl.teksavvy.com (206.248.155.109)  9.333 ms  9.124 ms xe-0-1-0-0-bdr01-mtl.teksavvy.com (192.171.63.17)  8.957 ms
 5  cloudflare.peer.qix.ca (198.179.18.55)  8.766 ms  8.584 ms  8.412 ms
 6  104.27.145.248 (104.27.145.248)  9.941 ms  10.217 ms  9.721 ms

traceroute says google.com is ~19 (or ~10 if you exclude "* * *") hops away. At the least, Google seems to be 5 hops beyond my ISP's network.

 

[PowerChaos]

If you want to make sure use following command
"Pathping google.com"

Sidenote. Pathping is Windows only command xd

Don't Ping the dns servers direcly but test a domain instead

IT Will calculate the ping in a set of time ( like 300 seconds )


Greets from PowerChaos
Verzonden vanaf mijn iPhone met Tapatalk

 

[laxboy10]

My point of mentioning the ping times was show the drastic difference in times and try to rule out some potential causes. The issue doesn't happen consistently but when it occurs internet is my house is unusable for periods of time.

 

[sfx2000]

Fun stuff... nping is part of nmap... what's fun with nping, is one can use an intermediary source...

Google is going to have a lot of different end-points out there as a result of their CDN architecture...

sfx@blaster:~$ sudo nping -c 1 --tcp -p 80,433 scanme.nmap.org www.google.com

Starting Nping 0.7.60SVN ( https://nmap.org/nping ) at 2017-08-26 15:12 PDT
SENT (0.0868s) TCP 192.168.1.20:33769 > 45.33.32.156:80 S ttl=64 id=28058 iplen=40  seq=1946170332 win=1480 
RCVD (0.1163s) TCP 45.33.32.156:80 > 192.168.1.20:33769 SA ttl=55 id=0 iplen=44  seq=2640600460 win=29200 <mss 1460>
SENT (1.0874s) TCP 192.168.1.20:33769 > 45.33.32.156:433 S ttl=64 id=28058 iplen=40  seq=1946170332 win=1480 
RCVD (1.1242s) TCP 45.33.32.156:433 > 192.168.1.20:33769 RA ttl=55 id=47205 iplen=40  seq=0 win=0 
SENT (2.0887s) TCP 192.168.1.20:33769 > 45.33.32.156:433 S ttl=64 id=28058 iplen=40  seq=1946170332 win=1480 
RCVD (2.1177s) TCP 45.33.32.156:433 > 192.168.1.20:33769 RA ttl=55 id=47246 iplen=40  seq=0 win=0 
SENT (3.0912s) TCP 192.168.1.20:33769 > 172.217.6.68:433 S ttl=64 id=28058 iplen=40  seq=1946170332 win=1480 

Statistics for host scanme.nmap.org (45.33.32.156):
 |  Probes Sent: 2 | Rcvd: 3 | Lost: -1  (922337203685477580800.00%)
 |_ Max rtt: 29.347ms | Min rtt: 28.858ms | Avg rtt: 29.184ms
Statistics for host www.google.com (172.217.6.68):
 |  Probes Sent: 2 | Rcvd: 0 | Lost: 2  (100.00%)
 |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 4 (160B) | Rcvd: 3 (138B) | Lost: 1 (25.00%)
Nping done: 2 IP addresses pinged in 4.13 seconds