Ping times Jan 28 onwards

[g7pkf]

Hi Dean

Try rebooting your router as that may get you onto a different pipe. The size of your Exchange is not really relevant because it is the size of the backhaul from the Exchange *compared* to the utilisation of that backhaul that is relevant. i.e. the large metro Exchanges have multiple high-capacity backhauls whereas a small, rural Exchange might have one, small backhaul.

Regards
Simon

oh do i have to?

every time i do that a pendoline goes past and i lose speed ive only just managed to get over my magic 4K mark......but if you insist here goes


if you don't here from me ive gone into the abyss

[g7pkf]

Remind me to never listen to people again.

ping times still cr*p.

sync down to  2089 (from 4209)

bugger.....

C:\Users\Dean>ping www.idnet.net -t

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=59ms TTL=59
Reply from 212.69.36.10: bytes=32 time=74ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=240ms TTL=59
Reply from 212.69.36.10: bytes=32 time=280ms TTL=59
Reply from 212.69.36.10: bytes=32 time=315ms TTL=59
Reply from 212.69.36.10: bytes=32 time=378ms TTL=59
Reply from 212.69.36.10: bytes=32 time=362ms TTL=59
Reply from 212.69.36.10: bytes=32 time=434ms TTL=59
Reply from 212.69.36.10: bytes=32 time=469ms TTL=59
Reply from 212.69.36.10: bytes=32 time=486ms TTL=59
Reply from 212.69.36.10: bytes=32 time=514ms TTL=59
Reply from 212.69.36.10: bytes=32 time=441ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59

Ping statistics for 212.69.36.10:
    Minimum = 14ms, Maximum = 514ms, Average = 90ms
Control-C
^C

[g7pkf]

gonna have to reboot router again at 5Am.....


think tin can and string good idea.

better than a pendolino train.

gonna get out the rocket launcher, beware delays on the euston-MK line

[Sebby]

Ouch. Your SNRM must seriously vary, Dean.

[Rik]

If you can just drop PPP, Dean, it often has a similar effect to re-booting without the risk of a profile drop.

[Glenn]

Looks like mine have risen from 23ms average to around 40ms

I think my exchange must get a little congested, the pings this morning are back at 23ms

[Rik]

I'm averaging 21ms this morning, Glenn, with little variation. My exchange does seem well provided, and we do have a node here as well, of course. If only I could persuade them to dump the aluminium, I'd be laughing.

[zappaDPJ]

I've did another 12 hour plot yesterday and the results are plain to see. For the first time in over two weeks my connection was stable, remarkably so in fact. The one blip was due to me having to remove the network cable for a minute or two.

If things stay like that I'll be over the moon so can you all keep off MY pipe please  

[attachment deleted by admin]

[Rik]

Time to change the axis scaling, Zappa.

Hey, you, get off of my pipe

[zappaDPJ]

Nice tune 

[Ham]

32 pages of this thread and 2 weeks later and pings are still cr*p
several phone calls to support they are aware of problems but seems to be unable to sort it out

i have been with idnet for nearly 3 years paying a bit more for a good service so realy want to stick with them as i know they are capable
of a good service but time going on i am considering calling for my MAC code

[Rik]

Hi Ham

For most people, pings have been sorted. If you're still having problems, talk to support again on Monday.

[Sebby]

Have you rebooted your router, Ham?

[neocr0n]

Latency is still high for me, it comes and goes through out the day.  It has been like this since a few days before this thread started and nothing much has changed.

It's no problem on my end either, rebooted yada yada yada.

Will phone them when monday rolls round, really not happy about this at all.

Just thought I'd weigh In so the few people still posting with problems know they aren't the only ones.

[Rik]

What does appear to be on the increase is congestion in the BT backhaul, particularly on smaller exchanges. Have you tried running something like PingGraph over a full day to get a picture of what the pattern is? This is my latest plot...

[attachment deleted by admin]

[Ham]

Hi Ham

For most people, pings have been sorted. If you're still having problems, talk to support again on Monday.

cant see the problem being fix tbh i still get bad pings but some times the pings settles and are good and then just go up and stay high
for ages before settleing down again

Have you rebooted your router, Ham?

yea tryed that serveral times too

[Rik]

My plots today look pretty much like the one above where, earlier in the week, there were long periods of spikes. IDNet are getting there from what I can see.

[Glenn]

This is my current plot

[attachment deleted by admin]

[Rik]

Mine is showing a few spikes, but the average is still good...

[attachment deleted by admin]

[4Way]

My ping has been getting better, abeit slowly,but just when I think it's been sorted out, it all goes pear shaped with spikes everwhere.

Rik, As you have spoken about a 24hr plot I assume that there are not any issues with running PingGraph for long periods, I mean from Idnet's point of view?

[Rik]

No, it only pings every 10 seconds, by default, 4Way, so unless everyone is doing it, it's not a problem. If you use the nameserver, as shown in my plot, you'll get a more accurate result as server load is not an issue at that point.

[4Way]

Thanks, I'l leave it running and send it into support tomorrow.

[Rik]

Great.

[zappaDPJ]

I've had another day of low pings and stability so hopefully there is now light at the end of the tunnel... or should I say pipe! 

[Rik]

Well, that's two of us sorted then, Zappa.