|
Re: High pings to London server.
my service has gone to pot again, pings all over the place at 5.30 am, did it following a poor 3mbit download.
1 88 ms 107 ms 12 ms 10.227.112.1
2 46 ms 124 ms 43 ms leic-t2cam1-b-ge914.inet.ntl.com [82.3.35.213]
3 40 ms 27 ms 45 ms leic-t2core-b-ge-210-0.inet.ntl.com [82.3.33.134]
4 24 ms 60 ms 12 ms nth-bb-b-so-230-0.inet.ntl.com [62.253.188.114]
5 73 ms 115 ms 10 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
6 116 ms 53 ms 127 ms 195.50.91.69
7 110 ms 37 ms 15 ms ge-11-0.ipcolo2.london1.level3.net [4.68.116.42]
8 17 ms 115 ms 113 ms 212.187.246.186
Default Gateway . . . . . . . . . : 86.13.36.1
Reply from 86.13.36.1: bytes=32 time=10ms TTL=255
Reply from 86.13.36.1: bytes=32 time=7ms TTL=255
Reply from 86.13.36.1: bytes=32 time=46ms TTL=255
Reply from 86.13.36.1: bytes=32 time=107ms TTL=255
Reply from 86.13.36.1: bytes=32 time=211ms TTL=255
Reply from 86.13.36.1: bytes=32 time=308ms TTL=255
Reply from 86.13.36.1: bytes=32 time=42ms TTL=255
Reply from 86.13.36.1: bytes=32 time=109ms TTL=255
Reply from 86.13.36.1: bytes=32 time=13ms TTL=255
Reply from 86.13.36.1: bytes=32 time=23ms TTL=255
Reply from 86.13.36.1: bytes=32 time=9ms TTL=255
Reply from 86.13.36.1: bytes=32 time=10ms TTL=255
Reply from 86.13.36.1: bytes=32 time=17ms TTL=255
Reply from 86.13.36.1: bytes=32 time=10ms TTL=255
Reply from 86.13.36.1: bytes=32 time=30ms TTL=255
Reply from 86.13.36.1: bytes=32 time=122ms TTL=255
Reply from 86.13.36.1: bytes=32 time=122ms TTL=255
Reply from 86.13.36.1: bytes=32 time=211ms TTL=255
Reply from 86.13.36.1: bytes=32 time=128ms TTL=255
|