Currently TS is getting some lag issues.
Quote from: R. Hayabusa on May 15, 2014, 06:17:54 PMCurrently TS is getting some lag issues.Kind of an odd phrasing considering your traceroutes show the lag originating in your own home / neighborhood.The reverse trace shows the same:|Host Loss% Snt Last Avg Best Wrst StDev|1. 67.228.69.113-static.reverse.softlayer.com 0.0% 1008 0.3 0.3 0.2 72.8 3.0|2. ae13.dar02.sr01.dal01.networklayer.com 0.0% 1008 0.2 0.2 0.1 41.0 2.6|3. ae6.bbr02.eq01.dal03.networklayer.com 0.0% 1008 0.2 1.5 0.2 57.1 6.8|4. ae-11.r01.dllstx04.us.bb.gin.ntt.net 0.0% 1008 0.7 0.7 0.5 26.4 1.0|5. ae-9.r07.dllstx09.us.bb.gin.ntt.net 0.0% 1007 0.7 0.7 0.6 10.6 0.5|6. 0.ae12.br2.dfw13.alter.net 0.0% 1007 0.7 3.2 0.3 67.3 9.8|7. P1-8-0-0.NYCMNY-LCR-21.verizon-gni.net 0.1% 1007 44.6 43.0 40.6 55.8 1.5|8. P1-0.NYCMNY-NYCXNYCR-ERXG02.verizon-gni.net 0.0% 1007 41.7 43.1 41.6 241.9 11.1|9. pool-71-190-xxx-xxx.nycmny.east.verizon.net 0.1% 1007 71.1 71.7 70.2 156.1 4.1 <- lag is here on the last hopIt's also unfortunate, that from your end, the route to Dallas on networklayer is taking a detour through Chicago. But that's separate from the lag that's already there from your first hop. (Or, last hop, in the above case.)