Can you post ping plotter image please to IP address 82.133.85.65

[Ermintrude]

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=149ms TTL=55
Reply from 82.133.85.65: bytes=32 time=147ms TTL=55
Reply from 82.133.85.65: bytes=32 time=194ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=85ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=63ms TTL=55
Reply from 82.133.85.65: bytes=32 time=10ms TTL=55
Reply from 82.133.85.65: bytes=32 time=222ms TTL=55
Reply from 82.133.85.65: bytes=32 time=29ms TTL=55
Reply from 82.133.85.65: bytes=32 time=11ms TTL=55
Reply from 82.133.85.65: bytes=32 time=247ms TTL=55
Reply from 82.133.85.65: bytes=32 time=185ms TTL=55
Reply from 82.133.85.65: bytes=32 time=25ms TTL=55
Reply from 82.133.85.65: bytes=32 time=204ms TTL=55
Reply from 82.133.85.65: bytes=32 time=11ms TTL=55
Reply from 82.133.85.65: bytes=32 time=10ms TTL=55
Reply from 82.133.85.65: bytes=32 time=58ms TTL=55
Reply from 82.133.85.65: bytes=32 time=70ms TTL=55
Reply from 82.133.85.65: bytes=32 time=77ms TTL=55

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 247ms, Average = 91ms

Watford, Herts.

[Sauron]

Pinging 82.133.85.65 with 32 bytes of data:



Reply from 82.133.85.65: bytes=32 time=36ms TTL=54

Reply from 82.133.85.65: bytes=32 time=15ms TTL=54

Reply from 82.133.85.65: bytes=32 time=15ms TTL=54

Reply from 82.133.85.65: bytes=32 time=12ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=15ms TTL=54

Reply from 82.133.85.65: bytes=32 time=15ms TTL=54

Reply from 82.133.85.65: bytes=32 time=24ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=14ms TTL=54

Reply from 82.133.85.65: bytes=32 time=14ms TTL=54

Reply from 82.133.85.65: bytes=32 time=14ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=12ms TTL=54

Reply from 82.133.85.65: bytes=32 time=17ms TTL=54

Reply from 82.133.85.65: bytes=32 time=12ms TTL=54

Reply from 82.133.85.65: bytes=32 time=13ms TTL=54

Reply from 82.133.85.65: bytes=32 time=14ms TTL=54



Ping statistics for 82.133.85.65:

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 12ms, Maximum = 36ms, Average = 15ms

[eth01]

Manchester:

Reply from 82.133.85.65: bytes=32 time=30ms TTL=53
Reply from 82.133.85.65: bytes=32 time=51ms TTL=53
Reply from 82.133.85.65: bytes=32 time=30ms TTL=53
Reply from 82.133.85.65: bytes=32 time=28ms TTL=53
Reply from 82.133.85.65: bytes=32 time=20ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=29ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=29ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Reply from 82.133.85.65: bytes=32 time=35ms TTL=53
Reply from 82.133.85.65: bytes=32 time=35ms TTL=53
Reply from 82.133.85.65: bytes=32 time=31ms TTL=53
Reply from 82.133.85.65: bytes=32 time=31ms TTL=53
Reply from 82.133.85.65: bytes=32 time=56ms TTL=53
Reply from 82.133.85.65: bytes=32 time=39ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=20ms TTL=53
Reply from 82.133.85.65: bytes=32 time=51ms TTL=53
Reply from 82.133.85.65: bytes=32 time=35ms TTL=53


US:

PING 82.133.85.65 (82.133.85.65) 56(84) bytes of data.
64 bytes from 82.133.85.65: icmp_seq=1 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=4 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=54 time=135 ms
64 bytes from 82.133.85.65: icmp_seq=8 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=9 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=10 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=11 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=12 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=13 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=14 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=15 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=16 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=17 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=18 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=19 ttl=54 time=136 ms
64 bytes from 82.133.85.65: icmp_seq=20 ttl=54 time=136 ms

[G UK]

Nottinghamshire NG17

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

F:\Users\G>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=15ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=18ms TTL=55
Reply from 82.133.85.65: bytes=32 time=57ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=13ms TTL=55
Reply from 82.133.85.65: bytes=32 time=22ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=14ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=26ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=58ms TTL=55
Reply from 82.133.85.65: bytes=32 time=21ms TTL=55
Reply from 82.133.85.65: bytes=32 time=25ms TTL=55
Reply from 82.133.85.65: bytes=32 time=15ms TTL=55
Reply from 82.133.85.65: bytes=32 time=39ms TTL=55
Reply from 82.133.85.65: bytes=32 time=35ms TTL=55
Reply from 82.133.85.65: bytes=32 time=15ms TTL=55

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 58ms, Average = 23ms

[Noggo]

Thanks for your input guys.

Almost everyone who has posted results apart from Jonathan90, has occasional spikes in lag, some worse that others.
(lucky git Jonathan90 and If I'm right in saying you're not to far from me. I'm in Kidderminster, I take it wolv. is Wolverhampton?)

I know ping ICMP requested are low priority when it comes to network traffic, but why straight after doing ping tests. I can load a game and connected to server and find the results where near as damn it the same. With spikes every second or so, sometimes more often and sometimes higher in value.

I was getting 18-25ms all the time peak or off-peak upto mid October last year, but since then it gone down hill and especially bad since Christmas.

This is a ping test done by a kind Gent who his on Plusnet ADSL. Although high in ms value, but hardly any difference between min and max values, which is what you need when it comes to gaming (very stable)
http://www.cableforum.co.uk/board/34460977-post9.html


My current results at 20:00 (Footies on so very good results for me tonight, with only 1 above 25ms at 37ms).
E:\Documents and Settings\Bob>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=25ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=22ms TTL=51
Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=22ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=21ms TTL=51
Reply from 82.133.85.65: bytes=32 time=21ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=23ms TTL=51
Reply from 82.133.85.65: bytes=32 time=37ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51
Reply from 82.133.85.65: bytes=32 time=20ms TTL=51

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 37ms, Average = 21ms


Does anyone know why almost everyone is getting these spikes?

Thanks again

Laters

[Cobbydaler]

ping -c 20 82.133.85.65
PING 82.133.85.65 (82.133.85.65) 56(84) bytes of data.
64 bytes from 82.133.85.65: icmp_seq=1 ttl=52 time=18.3 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=52 time=17.6 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=52 time=15.6 ms
64 bytes from 82.133.85.65: icmp_seq=4 ttl=52 time=17.7 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=52 time=17.1 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=52 time=17.7 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=52 time=17.6 ms
64 bytes from 82.133.85.65: icmp_seq=8 ttl=52 time=18.6 ms
64 bytes from 82.133.85.65: icmp_seq=9 ttl=52 time=18.1 ms
64 bytes from 82.133.85.65: icmp_seq=10 ttl=52 time=17.0 ms
64 bytes from 82.133.85.65: icmp_seq=11 ttl=52 time=17.6 ms
64 bytes from 82.133.85.65: icmp_seq=12 ttl=52 time=17.8 ms
64 bytes from 82.133.85.65: icmp_seq=13 ttl=52 time=16.4 ms
64 bytes from 82.133.85.65: icmp_seq=14 ttl=52 time=18.6 ms
64 bytes from 82.133.85.65: icmp_seq=15 ttl=52 time=17.7 ms
64 bytes from 82.133.85.65: icmp_seq=16 ttl=52 time=19.7 ms
64 bytes from 82.133.85.65: icmp_seq=17 ttl=52 time=17.8 ms
64 bytes from 82.133.85.65: icmp_seq=18 ttl=52 time=17.7 ms
64 bytes from 82.133.85.65: icmp_seq=19 ttl=52 time=17.6 ms
64 bytes from 82.133.85.65: icmp_seq=20 ttl=52 time=21.3 ms

--- 82.133.85.65 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19000ms
rtt min/avg/max/mdev = 15.678/17.922/21.339/1.123 ms

Ashton under Lyne
cpc2-asht1-0-0-custxxx.manc.cable.ntl.com

[Ben B]

Right, at home now on VM Connection. UBR: cpc1-oldh3-0-0-cust***.manc.cable.ntl.com

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ben>ping 82.133.85.65

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=228ms TTL=53
Reply from 82.133.85.65: bytes=32 time=153ms TTL=53
Reply from 82.133.85.65: bytes=32 time=31ms TTL=53
Reply from 82.133.85.65: bytes=32 time=45ms TTL=53

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 228ms, Average = 114ms

C:\Documents and Settings\Ben>

[AmAtoL]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Paul>ping 82.133.85.65 -n 20
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=50ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=42ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=57ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=29ms TTL=53
Reply from 82.133.85.65: bytes=32 time=52ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=20ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 57ms, Average = 25ms

That's mine from Stockport, a bit up and down, which tells more of a story than the average time at the end. A spread of over 40 isn't real good. A stable 40 is ok and a stable 14 is ok, just the up and down we can't get along with.

[browney]

C:\Users\Steven Brown>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=21ms TTL=54
Reply from 82.133.85.65: bytes=32 time=17ms TTL=54
Reply from 82.133.85.65: bytes=32 time=19ms TTL=54
Reply from 82.133.85.65: bytes=32 time=23ms TTL=54
Reply from 82.133.85.65: bytes=32 time=18ms TTL=54
Reply from 82.133.85.65: bytes=32 time=21ms TTL=54
Reply from 82.133.85.65: bytes=32 time=17ms TTL=54
Reply from 82.133.85.65: bytes=32 time=19ms TTL=54
Reply from 82.133.85.65: bytes=32 time=46ms TTL=54
Reply from 82.133.85.65: bytes=32 time=18ms TTL=54
Reply from 82.133.85.65: bytes=32 time=20ms TTL=54
Reply from 82.133.85.65: bytes=32 time=79ms TTL=54
Reply from 82.133.85.65: bytes=32 time=21ms TTL=54
Reply from 82.133.85.65: bytes=32 time=18ms TTL=54
Reply from 82.133.85.65: bytes=32 time=21ms TTL=54
Reply from 82.133.85.65: bytes=32 time=25ms TTL=54
Reply from 82.133.85.65: bytes=32 time=21ms TTL=54
Reply from 82.133.85.65: bytes=32 time=19ms TTL=54
Reply from 82.133.85.65: bytes=32 time=19ms TTL=54
Reply from 82.133.85.65: bytes=32 time=15ms TTL=54

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 79ms, Average = 23ms

[xpod]

Ma heart is back hame oan the Bonnie Banks but ma ping.......is fae SE Landon...innit

dad@home1:~$ ping -c 20 82.133.85.65
PING 82.133.85.65 (82.133.85.65) 56(84) bytes of data.
64 bytes from 82.133.85.65: icmp_seq=1 ttl=53 time=27.6 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=53 time=15.1 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=53 time=14.6 ms
64 bytes from 82.133.85.65: icmp_seq=4 ttl=53 time=17.2 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=53 time=50.8 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=53 time=47.5 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=53 time=52.0 ms
64 bytes from 82.133.85.65: icmp_seq=8 ttl=53 time=29.1 ms
64 bytes from 82.133.85.65: icmp_seq=9 ttl=53 time=15.2 ms
64 bytes from 82.133.85.65: icmp_seq=10 ttl=53 time=18.1 ms
64 bytes from 82.133.85.65: icmp_seq=11 ttl=53 time=16.6 ms
64 bytes from 82.133.85.65: icmp_seq=12 ttl=53 time=18.9 ms
64 bytes from 82.133.85.65: icmp_seq=13 ttl=53 time=28.4 ms
64 bytes from 82.133.85.65: icmp_seq=14 ttl=53 time=14.9 ms
64 bytes from 82.133.85.65: icmp_seq=15 ttl=53 time=16.7 ms
64 bytes from 82.133.85.65: icmp_seq=16 ttl=53 time=18.1 ms
64 bytes from 82.133.85.65: icmp_seq=17 ttl=53 time=26.1 ms
64 bytes from 82.133.85.65: icmp_seq=18 ttl=53 time=20.9 ms
64 bytes from 82.133.85.65: icmp_seq=19 ttl=53 time=17.5 ms
64 bytes from 82.133.85.65: icmp_seq=20 ttl=53 time=16.9 ms

--- 82.133.85.65 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19036ms
rtt min/avg/max/mdev = 14.648/24.157/52.069/11.817 ms
dad@home1:~$

I`ve got a spare ip/connection if any of you would be hac....crackers/skiddies fancy a go

Beware of the dog though

[Jonathan90]

The reason being if i am right is that your ubr is more laoded than mine i do find my ping does go up to about 19 21 on saturdays because the load is higher thats just my opinion

[SMHarman]

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=93ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=93ms TTL=51
Reply from 82.133.85.65: bytes=32 time=113ms TTL=51
Reply from 82.133.85.65: bytes=32 time=93ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=96ms TTL=51
Reply from 82.133.85.65: bytes=32 time=95ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=96ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 113ms, Average = 95ms

Where is the server. Mine was from Hoboken, NJ, USA

[Sirpingalot]

Originally Posted by zinglebarb

is that your ip address? wanna get hacked mate?

How would pinging yourself return results of 25ms and above? ;p

---------- Post added at 08:50 ---------- Previous post was at 08:40 ----------

C:\Documents and Settings\Administrator>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=30ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53

On the Baguley server.

he may have been pinging his home ip from a works address or from somewhere else . As there wasnt information on the IP and it was left for the membership to find out the location of the IP could have been anyones. For all we know he could have been posting someones ip deliberately in the hope someone malicious looked by. All I did was saw an IP that was obviously physical and point out the risks involved ,ok it turns out to be a game server which should be secure but on reading the thread I did not do that. Its upto the OP to put all the information required in a post not the readers job to do homework on it to ensure its ok or not

Can we stop debating the IP address now please.

No problems to it from here ;

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=15ms TTL=54
Reply from 82.133.85.65: bytes=32 time=17ms TTL=54
Reply from 82.133.85.65: bytes=32 time=15ms TTL=54
Reply from 82.133.85.65: bytes=32 time=17ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=33ms TTL=54
Reply from 82.133.85.65: bytes=32 time=20ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=35ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=14ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=27ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=16ms TTL=54

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 35ms, Average = 19ms