Well this fix was short lived
Quote:
Tracing route to 212.187.246.186 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms WRT54GS [192.168.**.***]
2 167 ms 181 ms 189 ms 10.9.0.1
3 311 ms 196 ms 240 ms oldh-t2cam1-b-ge-wan51-129.inet.ntl.com [80.5.16
5.109]
4 192 ms 205 ms 215 ms manc-t3core-1b-ge-011-0.inet.ntl.com [213.104.24
2.169]
5 268 ms 219 ms 201 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245]
6 311 ms 314 ms 315 ms man-bb-a-ae0-0.inet.ntl.com [62.253.187.177]
7 233 ms 211 ms 215 ms 212.187.137.1
8 330 ms 210 ms 257 ms so-6-1-0.mp2.manchesteruk1.level3.net [4.68.113.
118]
9 173 ms 213 ms 210 ms ae-1-0.bbr2.london1.level3.net [212.187.128.57]
10 289 ms 222 ms 200 ms ge-11-0.ipcolo2.london1.level3.net [4.68.116.42]
11 293 ms 265 ms 212 ms 212.187.246.186
Trace complete.
Pinging 212.187.246.186 with 32 bytes of data:
Reply from 212.187.246.186: bytes=32 time=187ms TTL=53
Reply from 212.187.246.186: bytes=32 time=185ms TTL=53
Reply from 212.187.246.186: bytes=32 time=206ms TTL=53
Reply from 212.187.246.186: bytes=32 time=220ms TTL=53
Ping statistics for 212.187.246.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 220ms, Average = 199ms
|