Ping times Jan 28 onwards

[conneh]

Ah ok
Thanks

[Rik]

NP.

[zappaDPJ]

Things were not at all good from my end today. In addition to high latency I started getting a lot of packet loss, 15% on average but as much as 30% to some locations and this was after a router reset. However having spoken to Simon (IDNet Support) he suggested another router restart and the results are plain to see (below). If you are still having problems try rebooting your router now.


Before:

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

C:\Users\zappaDPJ>ping multiplay.co.uk -n 50

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Reply from 85.236.96.22: bytes=32 time=158ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Reply from 85.236.96.22: bytes=32 time=156ms TTL=124
Reply from 85.236.96.22: bytes=32 time=157ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=163ms TTL=124
Reply from 85.236.96.22: bytes=32 time=150ms TTL=124
Reply from 85.236.96.22: bytes=32 time=155ms TTL=124
Reply from 85.236.96.22: bytes=32 time=142ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=157ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=157ms TTL=124
Reply from 85.236.96.22: bytes=32 time=153ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=162ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=155ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=158ms TTL=124
Reply from 85.236.96.22: bytes=32 time=157ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=154ms TTL=124
Reply from 85.236.96.22: bytes=32 time=155ms TTL=124
Reply from 85.236.96.22: bytes=32 time=154ms TTL=124
Request timed out.
Request timed out.
Reply from 85.236.96.22: bytes=32 time=156ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=157ms TTL=124
Reply from 85.236.96.22: bytes=32 time=156ms TTL=124
Reply from 85.236.96.22: bytes=32 time=158ms TTL=124
Reply from 85.236.96.22: bytes=32 time=156ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Reply from 85.236.96.22: bytes=32 time=152ms TTL=124
Reply from 85.236.96.22: bytes=32 time=156ms TTL=124
Reply from 85.236.96.22: bytes=32 time=158ms TTL=124
Reply from 85.236.96.22: bytes=32 time=160ms TTL=124

Ping statistics for 85.236.96.22:
    Packets: Sent = 50, Received = 43, Lost = 7 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 163ms, Average = 157ms

c:\Users\zappaDPJ>

After:

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

C:\Users\zappaDPJ>ping www.multiplay.co.uk -n 50

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=11ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=16ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=14ms TTL=124
Reply from 85.236.96.22: bytes=32 time=12ms TTL=124
Reply from 85.236.96.22: bytes=32 time=15ms TTL=124
Reply from 85.236.96.22: bytes=32 time=13ms TTL=124

Ping statistics for 85.236.96.22:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 16ms, Average = 13ms

C:\Users\zappaDPJ>

[Rik]

Thanks, Zappa, that's about the difference I saw.

[Joel]

hey all didn't want to start a new topic.

my ping is up 300 or so.

used to ping about 30/40 to London from Brighton (where I am), now im pinging more like 340.

Is something up? My download/upload is slowing as well...

I take it this isnt a problem on my end - a router reset didnt help 

thanks.

[Sebby]

Yep, something's up - you may want to have a read of the rest of the thread. Rebooting your router may sort it.

Oh, and

[Rik]

Welcome to the forum, Joel.

There has been a problem with the IDNet network at lunchtime today, which kicked everyone off for an hour. Details are hard to come by at the moment, but it involved the new router which was installed last week. As a result of this, as best I can judge, the previous work at re-balancing the network went out the window as everyone re-connected pretty much at the same time.

I have found, as have several others, that re-initiating the PPP session (or re-booting the router) has cured both throughput and ping times. If it still isn't working for you, have a word with support.

[DarkStar]

It's not stupid. There are two elements to your connection, the ADSL link, the connection between you and the exchange (which governs your speed), and the PPP session, your connection into IDNet and thus the web. It was the PPP which failed due to the router issue. Some routers will allow you to reset the PPP session independently of the ADSL connection. If you can do this, it has the advantage of not disturbing the connection speed.

Rik,
This resetting PPP session. I have a Netgear DG834, if I open up the connection status I see Connect and Disconnect. Do I simply Disconnect and then Connect? I have only had a Netgear a couple of weeks, havn't sassed it out properly yet.

[mrapoc]

Resetting the PPP got me back to "normal" pings (50ms)

Turns out I also have interleaving which is going to be off in next 24 hours..

didnt know it increased ping by like 30ms

[Rik]

It can be much worse than that, Sam, depending on the depth in use.

[vitriol]

ack

C:\Users\vitriol>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=168ms TTL=59
Reply from 212.69.36.10: bytes=32 time=168ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms 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 = 165ms, Maximum = 168ms, Average = 167ms

Going to try a router reboot.  Post back again soon.

[Rik]

Rik,
This resetting PPP session. I have a Netgear DG834, if I open up the connection status I see Connect and Disconnect. Do I simply Disconnect and then Connect? I have only had a Netgear a couple of weeks, havn't sassed it out properly yet.

On a Netgear, Ian, you have to do the whole re-sync thing, unfortunately, it doesn't allow you to just drop the PPP.

[Rik]

Going to try a router reboot.  Post back again soon.

We'll be here. (I hope  )

[Colin Burns]

my net connection is seeming slugish so was wonder if Idnet were still having issues here are some examples of my ping times.

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

C:\Documents and Settings\colin>ping idnet.com

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

Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms 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 = 165ms, Maximum = 175ms, Average = 170ms

C:\Documents and Settings\colin>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=162ms TTL=121
Reply from 212.58.224.138: bytes=32 time=166ms TTL=121
Reply from 212.58.224.138: bytes=32 time=151ms TTL=121
Reply from 212.58.224.138: bytes=32 time=161ms TTL=121

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

C:\Documents and Settings\colin>im thinking they may be just a little high as they are normaly at 30ms ish

[Joel]

ah, I just popped to the router - everything went off (not in my control), and then I am now back to normal speed.

Ping is important to me, I do a lot of gaming 

I think the problem resolved itself, and this is, without a doubt, the first time I have had a problem, which isn't solved by a router reboot, in 2 years.

Good work guys.

And thanks for the karma

[Rik]

Have you tried rebooting your router, Colin?

[vitriol]

C:\Users\vitriol>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=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms 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 = 22ms, Maximum = 24ms, Average = 23ms

Wonder how long it will last?

[trophymick]

\mick>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=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms 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 = 40ms, Maximum = 42ms, Average = 40ms

Is this OK?

[Rik]

Mine's been good for about three hours now.

[Sebby]

I wonder if it would be a good idea for IDNet to force everyone to reconnect to balance the centrals. Enta used to do it and it did work.

[Rik]

Is this OK?

Probably, Mick. Do you know what your 'normal' ping time is?

[Rik]

I wonder if it would be a good idea for IDNet to force everyone to reconnect to balance the centrals. Enta used to do it and it did work.

I thought they did at lunchtime. 

[Sebby]

[davej99]

Rik,
This resetting PPP session. I have a Netgear DG834, if I open up the connection status I see Connect and Disconnect. Do I simply Disconnect and then Connect? I have only had a Netgear a couple of weeks, havn't sassed it out properly yet.

I have a DG834 (GSP) and can and do disconnect as suggested above, going through CHAP authentication from the start. Does that not do the trick?

[Rik]

I don't know, tbh, Dave. The Netgear's I have had, like Ian's, only offered a connect/disconnect and I think that dropped the line and forced a resync.