Ping times Jan 28 onwards

[Sebby]

It shouldn't do, no, but things aren't quite right at IDNet.

[Glenn]

It seems to be settling down again

[Rik]

Does a router require 5+ reboots a day ? As in the other post everything has been very stable since the capacity and router swap.  Something is wrong somewhere unless the routing is still converging.

I can't answer that, tbh. I've re-booted my router more in the past week than I have in the past two years, and some of the time it has helped. In the absence of anything definitive from IDNet, it's the only suggestion for self-help that I can make.

[VaderDSL]

Bah, bad pings here as well for most of the weekend, am suffering PPP drop outs as well, it has been rock solid for a long time, sadly the upgrades recently have somewhat unsettled things, I really hope it settles down soon

[Glenn]

I think we all do

[davee]

just to let guys know, still bad pings also for me.   extremely flucuating pings, then remains high pings.   

[Rik]

This is my plot for the past hour...


[attachment deleted by admin]

[Steve]

Mine were ok for about an hour then went up again. It does feel like we all end up eventually using the same pipe

[Rik]

Weird and frustrating, eh Steve.

[Glenn]

I agree, I just rebooted my router twice, I'm now getting 130ms + pings

[Rik]

That sounds like what happened to me yesterday, Glenn, Simon was watching as I re-booted, and I re-connected to the same central.

[mrapoc]

I cannot game with pings 150ms onwards

Its not very fun at all

When will this be sorted? Im getting a bit impatient - have they made any statements lately?

[Rik]

They haven't, Sam.

[zappaDPJ]

I just restarted my router because my latency was rising by the minute. Apologies for the wall of text but this paints an interesting picture. High latency, no P/L pre reset followed by low latency with some P/L after the reboot. Not what I would have expected really.

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

C:\Users\zappaDPJ>ping www.idnet.com -n 50

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=155ms TTL=59
Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=123ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=78ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=158ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59

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

C:\Users\zappaDPJ>ping www.idnet.com -n 50

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 30ms, Average = 13ms

C:\Users\zappaDPJ>

[uxbod]

I have setup smokeping to keep an eye on things :-

IDNET SmokePing

[Rik]

Not seeing anything there.

[uxbod]

Try again Rik

[Rik]

No, just idnet.net and a blank screen.

[uxbod]

Doh! Darn split DNS *Should* be fine now !

[Aaron]

Pings still going from bad to normal then bad quite frequently, its bad right now with 100-200ms. Rebooting hasn't resolved it in this case.

Any update from IDNet? Their last was on 2009-02-02 on the status page.

[Rik]

Now I have it. My pings have collapsed in the past hour.

[attachment deleted by admin]

[mrapoc]

Works now  

Im getting really frustrated as of now

Thought it would have been sorted whilst i was away at the weekend

[hellyl]

Heya All

Just thought I would log in and say I have been suffering from similar issues as most people on here, seem to only log on here when I have a problem, which fortunately doesn't seem that often, although of late the high pings are becoming more and more of an issue.  My other half is a gaming man, and needs the connection in the evening, I use a laptop on the wireless network.  I am finding that I can't even surf seemingly low gfx sites without affecting the ping so he notices it in gameplay.  We have done the reboots of the router, more this past few days than any other time.  To be honest it doesn't seem to make a great deal of difference.  Hoping things get sorted soon, same as everyone else!


thought would add my speedtest, 20 mins ago I got a 43 ms ping - very irregular.  Quite hard to snipe on CODwaw with a connection interupt so I am informed! My hubbys shouts "what you doing on the net now?" will forever haunt me too!!

Helen x

[Rik]

Hi Helen

We all hope it gets sorted, not least IDNet I suspect.

[Philip]

Will the fact that everyone and their dog seems to be pinging idnet at the moment have an adverse effect? Or am I just being dim as usual