Quote:
|
Originally Posted by James Henry
Try another traceroute 
Seems a bit 'sudden' that increase to be congestion on the ntl side.
It's also a bit too stable. |
this was taken just after I was kicked on CS for high pings by the server.
Quote:
Tracing route to 212.187.246.186 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms WRT54GS
2 7 ms 7 ms 7 ms 10.9.0.1
3 270 ms 214 ms 289 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 197 ms 9 ms 9 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 260 ms 55 ms 10 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
6 349 ms 9 ms 9 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
7 296 ms 294 ms 291 ms 212.187.137.1
8 10 ms 9 ms 9 ms so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.
118]
9 483 ms 289 ms 296 ms so-1-1-0.bbr1.london1.level3.net [4.68.128.73]
10 472 ms 277 ms 290 ms ge-11-0.ipcolo2.london1.level3.net [4.68.116.42]
11 407 ms * 24 ms 212.187.246.186
Trace complete.
|