Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
bgotapen said:
I wonder does afrihost management even know about the constant latency/packetloss issues on your network?

Let me just show you an example:

You have afrigamer servers for counter strike global offensive? I can only see them on my webafrica capped or telkom uncapped. Your network does not let me see your own servers.

I have issues even when the network is supposedly fine. IPC issues could be a excuse if it was completely and totally out of afrihosts control.

but it isn't :)
Click to expand...

Hi

Our gaming servers are still a work in progress from our end :)
Do you have any tests results showing the high latency that I can investigate?
 
Orihalcon said:
Agreed. It does.

Whether that is not intended or not, it still causes it.
Click to expand...

Not the way shaping is implemented on our network.
When your account is shaped, P2P and Downloads are shaped - the actual protocol is affected here. So if you are to run tests which show latency (an MTR, traceroute etc) the latency is the same.

Remember that latency is a measurement that shows how much time it takes for data packets to communicate.

While shaping will slow down P2P when shaping is applied, it doesn't slow down the actual data communication.
 
Orihalcon said:
Agreed. It does.

Whether that is not intended or not, it still causes it.
Click to expand...

If server needs to send 20KB of game data to the client, and that traffic is shaped, then that data takes much longer to reach the client than it should - which introduces in-game latency.

Afripeople here seem to want to use latency in the pure technical sense of the term, while customers use the term to refer to in-game response time.
Fact is, when I was experiencing shaping of D3 traffic (yes, I was, Afrifolks), in-game latency measurement spiked over 2000ms.

So while shaping may not introduce latency in the context of pings and traceroutes, it DEFINITELY delays game data reaching your client, which is bad.
 
AfriGuy said:
Not the way shaping is implemented on our network.
When your account is shaped, P2P and Downloads are shaped - the actual protocol is affected here. So if you are to run tests which show latency (an MTR, traceroute etc) the latency is the same.

Remember that latency is a measurement that shows how much time it takes for data packets to communicate.

While shaping will slow down P2P when shaping is applied, it doesn't slow down the actual data communication.
Click to expand...

Um. Read that part again. Seriously.
Read it aloud to yourself. Does it make sense? The very purpose of shaping is to slow down the actual data communication of affected packets - usually by either queuing them or dropping them, forcing tcp backoff and window resizing.
 
Sinbad said:
If server needs to send 20KB of game data to the client, and that traffic is shaped, then that data takes much longer to reach the client than it should - which introduces in-game latency.

Afripeople here seem to want to use latency in the pure technical sense of the term, while customers use the term to refer to in-game response time.
Fact is, when I was experiencing shaping of D3 traffic (yes, I was, Afrifolks), in-game latency measurement spiked over 2000ms.

So while shaping may not introduce latency in the context of pings and traceroutes, it DEFINITELY delays game data reaching your client, which is bad.
Click to expand...
This.
 
Sinbad said:
Um. Read that part again. Seriously.
Read it aloud to yourself. Does it make sense? The very purpose of shaping is to slow down the actual data communication of affected packets - usually by either queuing them or dropping them, forcing tcp backoff and window resizing.
Click to expand...

If a protocol is shaped, the time an ICMP packet takes to get from point A to point B is the same compared to it being unshaped.
So if your Uncapped is shaped, your browsing, streaming and other realtime services don't see any increase in latency.
 
AfriGuy said:
If a protocol is shaped, the time an ICMP packet takes to get from point A to point B is the same compared to it being unshaped.
So if your Uncapped is shaped, your browsing, streaming and other realtime services don't see any increase in latency.
Click to expand...

ICMP is not the only protocol that can experience latency. ICMP is also irrelevant in the context of shaping of TCP connections.

Your TCP traffic can ALSO experience latency - round trip time from transmission of packet from server, to receipt by your client, transmission of ACK packet by client, to receipt by the server. And if one of those packets is at the back of a shaping queue, that round-trip time is going to be a lot longer than it should.
 
AfriGuy said:
Hi

Our gaming servers are still a work in progress from our end :)
Do you have any tests results showing the high latency that I can investigate?
Click to expand...


I can't see your servers :erm:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>tracert afrihost.co.za

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 10 ms 11 ms 105-236-6-193-esr-lo.mtnbusiness.co.za [105.236.
6.193]
3 25 ms 18 ms 21 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 79 ms 21 ms 19 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 72 ms 18 ms 21 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 94 ms 67 ms 19 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 42 ms 68 ms 22 ms 196.44.31.99
8 19 ms 22 ms 58 ms 196.31.220.8
9 39 ms 73 ms 77 ms 196.31.220.25
10 81 ms 57 ms 172 ms 196.31.63.206
11 19 ms 19 ms 19 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 34 ms 20 ms 36 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Chris>
 
uhm when i signed up to afrihost I remember i read that gaming or youtube is never shaped.

If you are shaping gaming. A definitive YES would be nice.
 
bgotapen said:
uhm when i signed up to afrihost I remember i read that gaming or youtube is never shaped.

If you are shaping gaming. A definitive YES would be nice.
Click to expand...

In my experience:
They don't intend to shape gaming, but through misconfiguration/miscalculation/mistake, they do sometimes.
 
bgotapen said:
uhm when i signed up to afrihost I remember i read that gaming or youtube is never shaped.

If you are shaping gaming. A definitive YES would be nice.
Click to expand...

Gaming and other realtime services like browsing, streaming, VoIP etc are not shaped.
 
bgotapen said:
I can't see your servers :erm:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>tracert afrihost.co.za

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 10 ms 11 ms 105-236-6-193-esr-lo.mtnbusiness.co.za [105.236.
6.193]
3 25 ms 18 ms 21 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 79 ms 21 ms 19 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 72 ms 18 ms 21 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 94 ms 67 ms 19 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 42 ms 68 ms 22 ms 196.44.31.99
8 19 ms 22 ms 58 ms 196.31.220.8
9 39 ms 73 ms 77 ms 196.31.220.25
10 81 ms 57 ms 172 ms 196.31.63.206
11 19 ms 19 ms 19 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 34 ms 20 ms 36 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Chris>
Click to expand...

These results look OK.
Could you mail our team the servers you can't see? I'll have our guys check it out to see what the issue is.
 
AfriGuy said:
These results look OK.
Could you mail our team the servers you can't see? I'll have our guys check it out to see what the issue is.
Click to expand...

What exactly looks ok to you in that test? Pings should not go over 25... that test shows massive PROBLEMS.... :erm:

Telkom with torrents blazing in the background:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>tracert afrihost.co.za

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 10 ms 13 ms 10 ms ti-224-112-01.telkomadsl.co.za [105.224.112.1]
3 24 ms 19 ms 19 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 19 ms 18 ms 19 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 20 ms 19 ms 20 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 19 ms 19 ms 19 ms rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za [196.
43.52.38]
7 19 ms 19 ms 19 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [1
96.43.25.138]
8 21 ms 21 ms 21 ms mtn-gw.telkom-ipnet.co.za [196.25.58.18]
9 29 ms 30 ms 22 ms 41.181.139.108
10 22 ms 22 ms 49 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
11 23 ms 22 ms 23 ms 196.30.1.53
12 23 ms 22 ms 22 ms 196.31.220.25
13 21 ms 20 ms 21 ms 196.31.63.206
14 41 ms 21 ms 21 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
15 1910 ms 329 ms 119 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Chris>ping telkom.co.za

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=22ms TTL=246
Reply from 196.43.22.222: bytes=32 time=22ms TTL=246
Reply from 196.43.22.222: bytes=32 time=22ms TTL=246
Reply from 196.43.22.222: bytes=32 time=22ms TTL=246

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

C:\Users\Chris>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 11 ms 11 ms 11 ms ti-224-112-01.telkomadsl.co.za [105.224.112.1]
3 20 ms 21 ms 19 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 19 ms 18 ms 18 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 20 ms 19 ms 19 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 19 ms 19 ms 19 ms 196.43.39.162
7 21 ms 20 ms 20 ms 196.43.23.6
8 21 ms 39 ms 23 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 22 ms 22 ms 22 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Chris>
 
lilggg said:
Lol you are complaining about a ping just over 25ms?
Click to expand...

read the rest it is spiking to 200's while it isn't on telkom

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>ping -n 30 afrihost.co.za

Pinging afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=196ms TTL=57
Reply from 197.242.144.102: bytes=32 time=75ms TTL=57
Request timed out.
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=35ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=97ms TTL=57
Reply from 197.242.144.102: bytes=32 time=38ms TTL=57
Reply from 197.242.144.102: bytes=32 time=18ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=29ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=75ms TTL=57
Reply from 197.242.144.102: bytes=32 time=91ms TTL=57
Reply from 197.242.144.102: bytes=32 time=73ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=18ms TTL=57
Reply from 197.242.144.102: bytes=32 time=26ms TTL=57
Reply from 197.242.144.102: bytes=32 time=90ms TTL=57
Reply from 197.242.144.102: bytes=32 time=29ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=50ms TTL=57
Reply from 197.242.144.102: bytes=32 time=37ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=52ms TTL=57
Reply from 197.242.144.102: bytes=32 time=112ms TTL=57
Reply from 197.242.144.102: bytes=32 time=143ms TTL=57

Ping statistics for 197.242.144.102:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 196ms, Average = 58ms

C:\Users\Chris>
 
Latency should be returning to normal in the North and South regions, we're still awaiting some final feedback for the increased latency in the East.
Could you guys keep testing please?
 
Still terrible

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>ping -n afrihost.co.za
Bad value for option -n, valid range is from 1 to 4294967295.

C:\Users\Chris>ping -n 100 afrihost.co.za

Pinging afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=44ms TTL=57
Reply from 197.242.144.102: bytes=32 time=54ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=141ms TTL=57
Reply from 197.242.144.102: bytes=32 time=39ms TTL=57
Reply from 197.242.144.102: bytes=32 time=56ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=90ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=36ms TTL=57
Reply from 197.242.144.102: bytes=32 time=26ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=42ms TTL=57
Reply from 197.242.144.102: bytes=32 time=55ms TTL=57
Reply from 197.242.144.102: bytes=32 time=59ms TTL=57
Reply from 197.242.144.102: bytes=32 time=92ms TTL=57
Reply from 197.242.144.102: bytes=32 time=98ms TTL=57
Reply from 197.242.144.102: bytes=32 time=142ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=70ms TTL=57
Reply from 197.242.144.102: bytes=32 time=107ms TTL=57
Reply from 197.242.144.102: bytes=32 time=81ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=53ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=18ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=35ms TTL=57
Reply from 197.242.144.102: bytes=32 time=91ms TTL=57
Reply from 197.242.144.102: bytes=32 time=58ms TTL=57
Reply from 197.242.144.102: bytes=32 time=98ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=51ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=45ms TTL=57
Reply from 197.242.144.102: bytes=32 time=91ms TTL=57
Reply from 197.242.144.102: bytes=32 time=83ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=146ms TTL=57
Reply from 197.242.144.102: bytes=32 time=84ms TTL=57
Reply from 197.242.144.102: bytes=32 time=78ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=48ms TTL=57
Reply from 197.242.144.102: bytes=32 time=27ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=27ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=28ms TTL=57
Reply from 197.242.144.102: bytes=32 time=47ms TTL=57
Reply from 197.242.144.102: bytes=32 time=112ms TTL=57
Reply from 197.242.144.102: bytes=32 time=69ms TTL=57
Reply from 197.242.144.102: bytes=32 time=60ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=75ms TTL=57
Reply from 197.242.144.102: bytes=32 time=40ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=74ms TTL=57
Reply from 197.242.144.102: bytes=32 time=177ms TTL=57
Reply from 197.242.144.102: bytes=32 time=95ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=130ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=38ms TTL=57
Reply from 197.242.144.102: bytes=32 time=82ms TTL=57
Reply from 197.242.144.102: bytes=32 time=63ms TTL=57
Reply from 197.242.144.102: bytes=32 time=33ms TTL=57
Reply from 197.242.144.102: bytes=32 time=86ms TTL=57
Reply from 197.242.144.102: bytes=32 time=28ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=36ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=49ms TTL=57
Reply from 197.242.144.102: bytes=32 time=55ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=45ms TTL=57
Reply from 197.242.144.102: bytes=32 time=40ms TTL=57

Ping statistics for 197.242.144.102:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 177ms, Average = 54ms

C:\Users\Chris>
 
bgotapen said:
Still terrible

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>ping -n afrihost.co.za
Bad value for option -n, valid range is from 1 to 4294967295.

C:\Users\Chris>ping -n 100 afrihost.co.za

Pinging afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=44ms TTL=57
Reply from 197.242.144.102: bytes=32 time=54ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=141ms TTL=57
Reply from 197.242.144.102: bytes=32 time=39ms TTL=57
Reply from 197.242.144.102: bytes=32 time=56ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=90ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=36ms TTL=57
Reply from 197.242.144.102: bytes=32 time=26ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=42ms TTL=57
Reply from 197.242.144.102: bytes=32 time=55ms TTL=57
Reply from 197.242.144.102: bytes=32 time=59ms TTL=57
Reply from 197.242.144.102: bytes=32 time=92ms TTL=57
Reply from 197.242.144.102: bytes=32 time=98ms TTL=57
Reply from 197.242.144.102: bytes=32 time=142ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=70ms TTL=57
Reply from 197.242.144.102: bytes=32 time=107ms TTL=57
Reply from 197.242.144.102: bytes=32 time=81ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=53ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=18ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=35ms TTL=57
Reply from 197.242.144.102: bytes=32 time=91ms TTL=57
Reply from 197.242.144.102: bytes=32 time=58ms TTL=57
Reply from 197.242.144.102: bytes=32 time=98ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=51ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=43ms TTL=57
Reply from 197.242.144.102: bytes=32 time=45ms TTL=57
Reply from 197.242.144.102: bytes=32 time=91ms TTL=57
Reply from 197.242.144.102: bytes=32 time=83ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=146ms TTL=57
Reply from 197.242.144.102: bytes=32 time=84ms TTL=57
Reply from 197.242.144.102: bytes=32 time=78ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=48ms TTL=57
Reply from 197.242.144.102: bytes=32 time=27ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=27ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=28ms TTL=57
Reply from 197.242.144.102: bytes=32 time=47ms TTL=57
Reply from 197.242.144.102: bytes=32 time=112ms TTL=57
Reply from 197.242.144.102: bytes=32 time=69ms TTL=57
Reply from 197.242.144.102: bytes=32 time=60ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=30ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=75ms TTL=57
Reply from 197.242.144.102: bytes=32 time=40ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=21ms TTL=57
Reply from 197.242.144.102: bytes=32 time=32ms TTL=57
Reply from 197.242.144.102: bytes=32 time=74ms TTL=57
Reply from 197.242.144.102: bytes=32 time=177ms TTL=57
Reply from 197.242.144.102: bytes=32 time=95ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=130ms TTL=57
Reply from 197.242.144.102: bytes=32 time=64ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=20ms TTL=57
Reply from 197.242.144.102: bytes=32 time=19ms TTL=57
Reply from 197.242.144.102: bytes=32 time=23ms TTL=57
Reply from 197.242.144.102: bytes=32 time=71ms TTL=57
Reply from 197.242.144.102: bytes=32 time=38ms TTL=57
Reply from 197.242.144.102: bytes=32 time=82ms TTL=57
Reply from 197.242.144.102: bytes=32 time=63ms TTL=57
Reply from 197.242.144.102: bytes=32 time=33ms TTL=57
Reply from 197.242.144.102: bytes=32 time=86ms TTL=57
Reply from 197.242.144.102: bytes=32 time=28ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=22ms TTL=57
Reply from 197.242.144.102: bytes=32 time=87ms TTL=57
Reply from 197.242.144.102: bytes=32 time=36ms TTL=57
Reply from 197.242.144.102: bytes=32 time=31ms TTL=57
Reply from 197.242.144.102: bytes=32 time=49ms TTL=57
Reply from 197.242.144.102: bytes=32 time=55ms TTL=57
Reply from 197.242.144.102: bytes=32 time=61ms TTL=57
Reply from 197.242.144.102: bytes=32 time=45ms TTL=57
Reply from 197.242.144.102: bytes=32 time=40ms TTL=57

Ping statistics for 197.242.144.102:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 177ms, Average = 54ms

C:\Users\Chris>
Click to expand...

Still very jumpy :(
What area are you in?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X