
Originally Posted by
XperiAnce
I can ping it on Mweb.
C:\Users\Michael>ping 64.150.160.27
Pinging 64.150.160.27 with 32 bytes of data:
Reply from 64.150.160.27: bytes=32 time=281ms TTL=49
Reply from 64.150.160.27: bytes=32 time=276ms TTL=49
Reply from 64.150.160.27: bytes=32 time=276ms TTL=49
Reply from 64.150.160.27: bytes=32 time=276ms TTL=49
Ping statistics for 64.150.160.27:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 276ms, Maximum = 281ms, Average = 277ms
C:\Users\Michael>tracert 64.150.160.27
Tracing route to teamxecuter.vpslink.com [64.150.160.27]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 9 ms 8 ms 9 ms 197-87-40-1.cpt.mweb.co.za [197.87.40.1]
3 9 ms 9 ms 9 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 9 ms 9 ms 9 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 205 ms 203 ms 203 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.
241]
6 204 ms 203 ms 203 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 204 ms 204 ms 203 ms 176.67.177.131
8 206 ms 201 ms 201 ms te1-4.ccr01.lon09.atlas.cogentco.com [149.6.98.5
]
9 281 ms 274 ms 274 ms te0-3-0-4.ccr22.lon01.atlas.cogentco.com [154.54
.36.169]
10 282 ms 274 ms 274 ms te0-1-0-4.ccr22.lon13.atlas.cogentco.com [154.54
.57.177]
11 281 ms 274 ms 273 ms 209.59.211.47
12 275 ms 274 ms 274 ms teamxecuter.vpslink.com [64.150.160.27]
Trace complete.
Bookmarks