High pings again

[Rik]

For sale notice to follow shortly.

[Wags]

The low ping didn't last long! It was fluctuating from 35 to 176 in COD4 (Maidenhead based server) tonight and eventually settling down to 35-60 by about 11.15pm. 
I am loathe to keep rebooting the router, especially as my sync rate then drops! I will keep my eye on this and drop support an email with some tracerts etc if this does not improve soon

[Sebby]

Yep, you must get in touch with support if it continues like this.

[Wags]

Not looking good tonight. Pings were 14-16ms earlier but now.....  

Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=143ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59

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

Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2    90 ms    93 ms   114 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3   153 ms   150 ms   128 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   111 ms   122 ms   123 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5   164 ms   173 ms   142 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6   104 ms   100 ms    97 ms  www.idnet.net [212.69.36.10]

Oh well, I'd better forget COD4 tonight and watch the History Channel....

[Gary]

Pings about 20ms higher here

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

C:\Users\****>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=58ms TTL=59
Reply from 212.69.36.10: bytes=32 time=65ms TTL=59

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

[juiceuk]

I saw the previous posts and thought I would check my latency tonight before having a game and I'm quite pleased I'm looking fine. A tad higher than my best but out of the 20 pings it only varies by 2ms and look very consistent.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59

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

[dujas]

I had three periods of high latency (130+ ping to www.idnet.net) yesterday, it tends to be temporary and a PPPoA reconnect usually returns service to normal if you don't want to wait.

[Gary]

High pings again 

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

C:\Users\>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59

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

[Fox]

I hate you Gary.......every time you seem to get bad ping, mine follows (and i think we live in entirely different parts of the country)


C:\Users\Fox>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=200ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59

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


but after exhaustive scientific research, I can only conclude that its all Rik's fault (he is sucking up all the bandwidth with his thousands of forum posts)  

[Rik]

 

But I'm on WBC, I don't have any impact on you peasants! 

[Wags]

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=59ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59

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

Still rather erratic. I usually get around 15ms on a cmd ping test. Last night in game pings eventually settled down at about10.30pm to 35-48 (COD4).  I am a peasant on ADSL Max (for Rik's benefit) . Dare I try playing tonight?

[Fox]

lol, you need to be careful Rik, the peasants may revolt (note to self, change forum name to Che) and you will have to live on turkey twizzlers and pot noodles

[Rik]

No, anything but the DR withdrawal! 

[Rik]

It's not IDNet as a whole:

ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59

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

but that's interleaved WBC.

If you haven't already, follow the ping diagnostics in the FAQ and let support have the results.

[Ray]

Fine on Max here; -

Pinging idnet.net with 32 bytes of data:
Reply from 212.69.36.10 bytes:32 Time:21ms TTL:59
Reply from 212.69.36.10 bytes:32 Time:21ms TTL:59
Reply from 212.69.36.10 bytes:32 Time:17ms TTL:59
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:59
Reply from 212.69.36.10 bytes:32 Time:16ms TTL:59
Ping statistics for idnet.net :
Packets: Sent = 5, Received = 5, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 27ms, Average = 20ms

[Gary]

I hate you Gary.......every time you seem to get bad ping, mine follows (and i think we live in entirely different parts of the country)


C:\Users\Fox>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=200ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59

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


but after exhaustive scientific research, I can only conclude that its all Rik's fault (he is sucking up all the bandwidth with his thousands of forum posts) 

Im sorry its my luck with electronics, I'm down on the south coast 

[Gary]

If you haven't already, follow the ping diagnostics in the FAQ and let support have the results.

I have given up doing that now, Rik it sorts itself out eventually  I just go and do something else

[dujas]

I had to reconnect again, about 10 minutes ago, due to high latency.

[Wags]

I have just emailed support, as this has been going on for too long now :

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=133ms TTL=59
Reply from 212.69.36.10: bytes=32 time=68ms TTL=59
Reply from 212.69.36.10: bytes=32 time=65ms TTL=59
Reply from 212.69.36.10: bytes=32 time=47ms TTL=59

Ping statistics for 212.69.36.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
   Minimum = 47ms, Maximum = 133ms, Average = 78ms

I will let you know what support have to say.
                           

[Gary]

Mine are back down now, about 2ms higher than usual so I'm happy

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

C:\Users\>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59

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

C:\Users\>

[Fox]

Yup mine are back to normal now (btw Gary I live in Yorkshire, just seems strange we always seem to get ping problems at the same time)

I think it was the threat of rationing Rik that did it (one look at a Tesco value sausage and he got scared)

[Simon]

[Rik]

(one look at a Tesco value sausage and he got scared)

You have no idea how bad it was, but I'm off the life-support system now.

[Wags]

I am most impressed - Simon answered my email at 2.32 am!!! That is real dedication to customer service!

Unfortunately, on occasions, we see that the traffic into us from BT 
has become un-balanced in that a single pipe has attracted too much 
traffic. We are continually working at keeping our BT pipes balanced 
but, when you experience such congestion, a reboot of your router 
should force your session onto a different pipe until we get the 
balancing corrected. Apologies for the inconvenience.

Regards
Simon

I will pop home at lunchtime and give the router a hard reboot and hope this sorts the problem.

[Rik]

He never sleeps.