Ping times Jan 28 onwards

[Colin Burns]

reboot sorted it out rik

[Sebby]

It does do the trick, Dave, but I believe it also causes you to lose sync. That in itself is not a bad thing as long as you don't do it too many times consecutively, which the exchange may see as instability.

[conneh]

Have rebooted my router a few times today, even unplugged it and left it for a while... These are my results.

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=163ms TTL=124
Reply from 85.236.96.22: bytes=32 time=159ms TTL=124
Request timed out.
Reply from 85.236.96.22: bytes=32 time=141ms TTL=124

Ping statistics for 85.236.96.22:
   Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
   Minimum = 141ms, Maximum = 163ms, Average = 154ms

[Rik]

You need to talk to IDNet, then, they can manually move you to a different pipe.

[Rik]

reboot sorted it out rik

Great.

[trophymick]

This is about normal for me at the moment, not much variation. (except for a total loss of service ) I'm happy with it, considering my location

[davej99]

It does do the trick, Dave, but I believe it also causes you to lose sync. That in itself is not a bad thing as long as you don't do it too many times consecutively, which the exchange may see as instability.

and Rik re Netgear rebooting.

Sync seems to hold, at least the green light stays on and "Show Stats" polling remains steady. But I have an oddball DG834GSPv3 Branson special.

[Rik]

In that case, all bets are off.

[davej99]

In that case, all bets are off.

Are you laughing at my oddball?

[Rik]

No, at the thought of betting on a Netgear. 

[Aaron]

Odd but rebooting the router fixed it, despite connecting to the same gateway as before. Pings are good now

[Rik]

Same gateway, different central.

[DarkStar]

Opened up connection status on my Netgear and Disconnected, waited 10secs or so and then Connected. Result below:

Ian



[attachment deleted by admin]

[Rik]

Is that about normal for you, Ian? That's similar to what happened to me, though I average around 24ms.

[Steve]

Mine was similar when I got home, rebooted the router,ping rates down nicely but still seeing a great variation in individual ping times which I presume is down to congestion.

[Rik]

Possible, Steve. I've got a few spikes now, but nothing untoward.

[DarkStar]

Is that about normal for you, Ian? That's similar to what happened to me, though I average around 24ms.

That is low for me, until this week I had never seen pings below 60>80. Tracert below

C:\Documents and Settings\Owner>tracert idnet.net

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

 1     1 ms    <1 ms    <1 ms  192.168.0.1
 2    38 ms   122 ms   121 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3    36 ms    37 ms    36 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    37 ms    36 ms    36 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    36 ms    37 ms    36 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    35 ms    35 ms    36 ms  www.idnet.net [212.69.36.10]

Speed is also back to normal - 200>250mbps. It was a quarter of that this afternoon.

Ian

[Rik]

Sounds like you've moved off the congested central.

[DarkStar]

Sounds like you've moved off the congested central.

Good, I just hope it stays this way

Ian

[davej99]

When I was with a centrally challenged ISP, we used to log on, check ping, log off, log on, check ping, etc till we got a central that was reasonable. One smart guy automated the process and eventually we all used the routine. I guess BT round robin the logons among an ISP's centrals.

[Steve]

I posted some poor ping times here,I have deleted them as I forgot the WHS was running utorrent

[Philip]

a lot better since my router reboot

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

C:\Users\Philip>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=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms 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 = 29ms, Maximum = 32ms, Average = 30ms

C:\Users\Philip>


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

C:\Users\Philip>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=35ms TTL=121
Reply from 212.58.224.138: bytes=32 time=30ms TTL=121
Reply from 212.58.224.138: bytes=32 time=40ms TTL=121
Reply from 212.58.224.138: bytes=32 time=29ms 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 = 29ms, Maximum = 40ms, Average = 33ms

C:\Users\Philip>

[Sebby]

When I was with a centrally challenged ISP, we used to log on, check ping, log off, log on, check ping, etc till we got a central that was reasonable. One smart guy automated the process and eventually we all used the routine. I guess BT round robin the logons among an ISP's centrals.

I think I know which ISP you are talking about as I was once with them too.

[davej99]

If that were true, it would be virgin on the ridiculous.     

[Simon]

Here's mine, after router reboot:

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

Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms 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 = 34ms, Maximum = 35ms, Average = 34ms

C:\Documents and Settings\Simon>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=33ms TTL=121
Reply from 212.58.224.138: bytes=32 time=32ms TTL=121
Reply from 212.58.224.138: bytes=32 time=35ms TTL=121
Reply from 212.58.224.138: bytes=32 time=35ms 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 = 32ms, Maximum = 35ms, Average = 33ms