Looking good here, I will be playing over the weekend so will see if it lasts.

I won't be So bad to day it's screwing up my web browsing.

[IMG]http://i645.photobucket.com/albums/uu176...[/IMG]

Edited by deleted (Sat 07-Feb-09 17:49:12)

Please reboot your router as that should get you onto a different pipe which should clear your problem.
Simon

I've done that and it is better now, thanks.

However, I did this the other day also when you first mentioned it and that also had the desire effect then, but the next afternoon the high pings were back. I probably wouldn't be averse to betting they'll be back tomorrow (or maybe Monday). Having to check the router stats and then reboot it every day isn't what I envisaged as a the overriding feature of a premium service! Are you able to say that this is a known ongoing problem which will be fixed soon?

That is our imperative and I should think we will lose many customers if we do not succeed.
Simon

Anyone else having problems tonight?



Pinging 217.146.86.46 with 32 bytes of data:

Reply from 217.146.86.46: bytes=32 time=114ms TTL=122
Reply from 217.146.86.46: bytes=32 time=93ms TTL=122
Reply from 217.146.86.46: bytes=32 time=121ms TTL=122
Reply from 217.146.86.46: bytes=32 time=71ms TTL=122
Reply from 217.146.86.46: bytes=32 time=73ms TTL=122
Reply from 217.146.86.46: bytes=32 time=90ms TTL=122
Reply from 217.146.86.46: bytes=32 time=91ms TTL=122
Reply from 217.146.86.46: bytes=32 time=106ms TTL=122
Reply from 217.146.86.46: bytes=32 time=111ms TTL=122
Reply from 217.146.86.46: bytes=32 time=118ms TTL=122
Reply from 217.146.86.46: bytes=32 time=139ms TTL=122
Reply from 217.146.86.46: bytes=32 time=107ms TTL=122
Reply from 217.146.86.46: bytes=32 time=118ms TTL=122
Reply from 217.146.86.46: bytes=32 time=149ms TTL=122
Reply from 217.146.86.46: bytes=32 time=137ms TTL=122
Reply from 217.146.86.46: bytes=32 time=162ms TTL=122
Reply from 217.146.86.46: bytes=32 time=182ms TTL=122
Reply from 217.146.86.46: bytes=32 time=136ms TTL=122
Reply from 217.146.86.46: bytes=32 time=137ms TTL=122
Reply from 217.146.86.46: bytes=32 time=175ms TTL=122
Reply from 217.146.86.46: bytes=32 time=167ms TTL=122
Reply from 217.146.86.46: bytes=32 time=152ms TTL=122
Reply from 217.146.86.46: bytes=32 time=134ms TTL=122
Reply from 217.146.86.46: bytes=32 time=158ms TTL=122
Reply from 217.146.86.46: bytes=32 time=156ms TTL=122
Reply from 217.146.86.46: bytes=32 time=153ms TTL=122
Reply from 217.146.86.46: bytes=32 time=144ms TTL=122
Reply from 217.146.86.46: bytes=32 time=139ms TTL=122
Reply from 217.146.86.46: bytes=32 time=113ms TTL=122
Reply from 217.146.86.46: bytes=32 time=130ms TTL=122
Reply from 217.146.86.46: bytes=32 time=186ms TTL=122

I rebooted the router and the PPP light didn't come on, I was surfing before I rebooted so I know it was working fine, after reboot noting worked so I rebooted again and the PPP light came on and I now get low pings again from the same address as above.

Strange.

Pinging 217.146.86.46 with 32 bytes of data:

Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=52ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=25ms TTL=122
Reply from 217.146.86.46: bytes=32 time=25ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=27ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=39ms TTL=122
Reply from 217.146.86.46: bytes=32 time=31ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=26ms TTL=122
Reply from 217.146.86.46: bytes=32 time=25ms TTL=122
Reply from 217.146.86.46: bytes=32 time=37ms TTL=122
Reply from 217.146.86.46: bytes=32 time=24ms TTL=122
Reply from 217.146.86.46: bytes=32 time=36ms TTL=122
Reply from 217.146.86.46: bytes=32 time=28ms TTL=122
Reply from 217.146.86.46: bytes=32 time=27ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46: bytes=32 time=31ms TTL=122
Reply from 217.146.86.46: bytes=32 time=23ms TTL=122
Reply from 217.146.86.46:

Edited by Jack_Hackett (Tue 10-Feb-09 19:00:49)

Same happened to me and same solution.

Well the latency issue still exists for me. I was sort of expecting that by the time I migrated away from Idnet (that should changeover today) that all would be sorted.
Yet every evening (bar one) in around the last 10 days pings have been all over the place regardless of router reboots.

Whilst I have had some excellent pings when Idnet has been working 100% ok over the last year probably bettering most other ISP's, I'm sort of pleased i'm about to migrate away as this has started to drive me nuts.

I still can't help but wonder if the unexplained outage last week is somehow connected to this ongoing problem, albeit in a remote unlikely way.