Latency issues

Steve · May 15, 2009, 16:08:44

Sluggish afternoon connected via .net pings to www.idnet.net at around 70ms cured by a router reboot and back down to 20ms, not seen this for a while.

Rik · May 15, 2009, 16:11:34

Same here, for the past two days my pings have 'gone out' from a 23ms average to a 31ms average, Steve.

vitriol · May 15, 2009, 17:11:48

Pings atm for me are a little increased 60ms. Normally they around 22ms.

Rik · May 15, 2009, 17:13:34

It might be worth trying a router reboot Vit, though I'd probably leave it till morning for the best speed.

zappaDPJ · May 15, 2009, 17:23:22

A steady 23-25ms to idnet.com for me at the moment.

Rik · May 15, 2009, 17:25:36

So not widespread, probably not geographical...

Steve · May 15, 2009, 17:27:03

Mine have stayed low since the reboot.I am not worried about the time of day due to presence of full sync and 15db margin.

Rik · May 15, 2009, 17:27:20

Ah shaddup.

Lance · May 15, 2009, 17:27:34

You can go right off some people...

edit - we need the negative karma to come back!

Rik · May 15, 2009, 17:32:00

We'll just pour it down Steve's line.

Steve · May 15, 2009, 17:33:33

In the recent past when we had balancing issues and the pings started creep upwards my throughput tended to fall as well, this was not the case today plus as I said the pings have remained low since the router reboot.

Lance · May 15, 2009, 17:45:17

My balancing issues tend to come after many pints of beer of have consumed!

Rik · May 15, 2009, 17:47:45

It doesn't take many for me.

vitriol · May 15, 2009, 18:38:37

Quote from: Rik on May 15, 2009, 17:13:34
It might be worth trying a router reboot Vit, though I'd probably leave it till morning for the best speed.

Sorted

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

Rik · May 15, 2009, 18:39:45

It makes you wonder what happens in the process, doesn't it. IOW, is it the router or the connection?

vitriol · May 15, 2009, 19:55:50

Not sure, dont have the time to start digging really.

Mohux_Jnr · May 19, 2009, 21:25:47

Maybe someone can enlighten me as to why we constantly now have to reboot our routers daily in order to reset an acceptable ping. I never had to do this pre-downgrade ( poor humour ). To say it is getting tiresome would be an understatement, it normally starts around 4pm and this time of day is definately the worse although recently it has continued through the evening sometimes requiring 3/4 reboots.

Is this likely to be sorted?, speaking for my connection the ping times have never been stable since the upgrade, and this evening has just about killed my patience waiting for a resolution.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms 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 = 121ms, Maximum = 164ms, Average = 140ms

Rebooted.........no change, rebooted for a second time and the pings are back to what I pray for

, but I can guarantee after an hour of gameplay it will require another reboot?.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms 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 = 15ms, Maximum = 17ms, Average = 15ms

Steve · May 19, 2009, 21:46:44

I can't enlighten you but I will agree that for me towards the end of last week my ping times were elevated to www.idnet.net @70ms this was cured by a reboot to 16 -25 ms. Today they've been around 35-40ms certainly not as good as they have been over the past few months.

Sebby · May 19, 2009, 22:08:21

All I can suggest is that you get in touch with IDNet and let them know what is happening, so that they can look into it.

Rik · May 20, 2009, 09:31:00

Quote from: Mohux_Jnr on May 19, 2009, 21:25:47
Maybe someone can enlighten me as to why we constantly now have to reboot our routers daily in order to reset an acceptable ping.

Most of us don't, Mo. I got hit by poor pings last Thursday, a reboot cured it and they've been fine since. My router had been 'up' for 35 days when I rebooted, and that was the first ping problem I'd seen since February, I think. Some people are having issues, but it's a relatively small number as best I can judge. As Sebby says, you really need to talk to IDNet so that they can check your line.

golden · May 20, 2009, 16:50:42

My ping is stable but exactly 10-15ms higher than yesterday and the previous months.

Rik · May 20, 2009, 16:54:08

Have you tried re-booting your router?

Gary · May 20, 2009, 19:30:28

My pings seem 20 ms higher, Rik. My router was rebooted about 5 days ago ish they are for idnet, 41ms and for bbc.co.uk 41ms also.

Gary · May 21, 2009, 09:09:37

Spoke to support and they have no idea why a reboot would lower your pings in fact it shouldn't make any difference I was told

Oh well, it may all change again in a day or two

Rik · May 21, 2009, 09:33:33

I don't understand why it often works, Gary, the only half-logical explanation I can come up with is that the new connection is routed differently.