cancel
Showing results for 
Search instead for 
Did you mean: 

High latency

philrule
Newbie
Posts: 8
Registered: ‎02-06-2010

High latency

I've been with plusnet for a few weeks now and had been hitting some high latency while gaming usually gone midnight but occassionally during the day too of around 1000ms when playing World of Warcraft on a US server which was generally resolved by rebooting the router. For the past 2 days the lag has been pretty much constant though, not just while gaming but when web browsing too. Included below is some traceroutes which seem to me to indicate the high latency is on the plusnet servers, I did a wireshark capture last night following the plusnet guide and saw that my World of Warcraft traffic is being correctly prioritised as gaming traffic though like I said this latency is affecting web browsing too. Let me know if any more information is required:
Tracing route to google.com [66.102.9.105]
over a maximum of 30 hops:
  1    1 ms    2 ms    2 ms  192.168.1.1
  2  230 ms  187 ms  306 ms  lo0-central3.pcl-ag04.plus.net [195.166.128.243]
  3  239 ms  238 ms  401 ms  gi1-11-431.pcl-gw01.plus.net [84.92.6.240]
  4  157 ms  221 ms  191 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  356 ms  238 ms  186 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    *      313 ms  378 ms  195.66.224.125
  7  145 ms  115 ms  263 ms  64.233.175.27
  8  199 ms  255 ms  233 ms  209.85.250.216
  9  227 ms  283 ms  157 ms  72.14.232.235
10  226 ms  168 ms  139 ms  64.233.174.14
11  127 ms  196 ms  232 ms  lm-in-f105.1e100.net [66.102.9.105]
Trace complete.

Tracing route to microsoft.com [207.46.197.32]
over a maximum of 30 hops:
  1    14 ms    5 ms    4 ms  192.168.1.1
  2  225 ms  120 ms  214 ms  lo0-central3.pcl-ag04.plus.net [195.166.128.243]
  3  213 ms  279 ms    *    gi1-11-431.pcl-gw01.plus.net [84.92.6.240]
  4  201 ms  562 ms  372 ms  te2-1.pcl-gw02.plus.net [212.159.1.114]
  5    *        *        *    Request timed out.
  6  313 ms  429 ms  188 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
  7  341 ms  262 ms    *    ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
  8  276 ms  211 ms  294 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
  9  123 ms  114 ms  153 ms  ae-1-51.edge2.NewYork2.Level3.net [4.69.138.195]
10  363 ms  378 ms  283 ms  MICROSOFT-C.edge2.NewYork2.Level3.net [4.71.190.2]
11  188 ms  237 ms  337 ms  209.240.199.194
12  265 ms  329 ms  233 ms  ge-7-0-0-0.nyc-64cb-1b.ntwk.msn.net [207.46.47.21]
13  285 ms  272 ms  259 ms  ge-0-1-0-0.blu-64c-1b.ntwk.msn.net [207.46.43.114]
14    *      310 ms  248 ms  xe-0-1-3-0.ch1-16c-1b.ntwk.msn.net [207.46.46.151]
15  335 ms  225 ms  220 ms  xe-0-0-0-0.ch1-16c-1a.ntwk.msn.net [207.46.43.142]
16  417 ms  381 ms  288 ms  ge-3-1-0-0.co1-64c-1a.ntwk.msn.net [207.46.46.118]
17  372 ms  308 ms  234 ms  ge-1-0-0-0.wst-64cb-1a.ntwk.msn.net [207.46.43.163]
18  296 ms  350 ms  338 ms  ge-1-1-0-0.cpk-64c-1a.ntwk.msn.net [207.46.46.239]
19    *      397 ms  352 ms  ten3-4.cpk-76c-1b.ntwk.msn.net [207.46.47.193]
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *