0
Here's an output for a mtr to google.com
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. Wireless_Broadband_Router.home 0.0% 59 2.0 11.3 1.8 105.3 18.9
3. lo0-100.NWRKNJ-VFTTP-332.verizon-gni.net 0.0% 59 7.3 11.1 3.8 33.7 6.6
4. T1-15-0-13.NWRKNJ-LCR-22.verizon-gni.net 0.0% 59 41.0 14.4 6.8 41.0 7.4
5. ???
6. ???
7. 0.ae6.GW2.EWR19.ALTER.NET 0.0% 58 14.3 18.1 6.2 52.0 10.9
8. GOOGLE-gw.customer.alter.net 0.0% 58 8.8 15.0 6.7 61.7 10.0
9. 54.14.117.63.piscataway.google-ggc.verizon.com 0.0% 58 12.1 15.4 6.5 46.2 7.7
As far as I can tell, it doesn't seem so bad. However, about 50% of the time I'm trying to access a website (e.g. google, Facebook, other reliable / fast sites), it will take several seconds before resolving the host
For example, this request to google.com:
Queueing 15.38 ms
Stalled 8.26 s
DNS Lookup 8.26 s
Initial connection 29.39 ms
SSL 21.18 ms
Request sent 0.21 ms
Waiting (TTFB) 120.38 ms
Content Download 671.17 ms
9.10 s
Can anyone explain why this happens, or even better, provide me with a solution?
4have you tried a different DNS server? – Keltari – 2015-12-05T21:31:34.940
2As @Keltari stated, try a couple of known good DNS servers (like 8.8.8.8 for example) and test your times ... if you're using your ISP's own DNS server, that could be the problem (my old ISP would do DNS redirects and injection, which added a LOT of delay to a simple lookup, so I switched to the open pools and my resolutions are always in the ms). – txtechhelp – 2015-12-05T21:34:03.843