Tracing route to 149.252.212.162.in-addr.arpa.static.cnservers.com [162.212.252. 149] over a maximum of 30 hops: 1 1 ms 5 ms 1 ms 192.168.178.1 2 10 ms 9 ms 10 ms 10.136.16.1 3 11 ms 10 ms 10 ms zw-lc0001-dr101-vl201.core.as9143.net [213.51.16 3.1] 4 20 ms 35 ms 12 ms vnn-rc0001-cr101-ae5-0.core.as9143.net [213.51.1 58.104] 5 39 ms 18 ms 23 ms asd-lc0006-cr101-ae6-0.core.as9143.net [213.51.1 58.78] 6 9 ms 10 ms 10 ms xe-8-1-0.edge3.Amsterdam1.Level3.net [212.72.33. 213] 7 13 ms 16 ms 8 ms Intelquint-level3-1x10G.Amsterdam.Level3.net [4. 68.70.98] 8 * * 153 ms xe-1-0-0.sea22.ip4.tinet.net [89.149.184.165] 9 155 ms 154 ms 154 ms cnservers-gw.ip4.tinet.net [173.241.128.178] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 166 ms 157 ms 158 ms 149.252.212.162.in-addr.arpa.static.cnservers.co m [162.212.252.149] Trace complete.
Well, that trace result shows that your latency to your own ISP is also good. So at the time of doing that traceroute, I don't think you should have been lagging at all. Maybe it was just luck, try doing it again the next time you are lagging.
