Ping times Jan 28 onwards

[Joel]

here are my ping times since 16th Jan.

no pattern



Blurred out ones are pings to melbourne and new york, for other reasons. I change between Maidenhead and London so often because that is the "Suggested" server at the time.

Ping time now is about 180 to london.

not good  

[Rik]

I wouldn't trust the pings from a speed test site, personally. I always ping the IDNet nameserver, 212.69.40.3, as this removes most variables from the equation.

[vitriol]

C:\Users\vitriol>ping 212.69.40.3

Pinging 212.69.40.3 with 32 bytes of data:
Reply from 212.69.40.3: bytes=32 time=22ms TTL=61
Reply from 212.69.40.3: bytes=32 time=21ms TTL=61
Reply from 212.69.40.3: bytes=32 time=22ms TTL=61
Reply from 212.69.40.3: bytes=32 time=22ms TTL=61

Ping statistics for 212.69.40.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 22ms, Average = 21ms

Looking good again, been stable for the last few days and gaming has been much improved.  Thank you IDNet !!!!

[Rik]

Very similar, Vit:

ping 212.69.40.3

Pinging 212.69.40.3 with 32 bytes of data:

Reply from 212.69.40.3: bytes=32 time=22ms TTL=61
Reply from 212.69.40.3: bytes=32 time=21ms TTL=61
Reply from 212.69.40.3: bytes=32 time=21ms TTL=61
Reply from 212.69.40.3: bytes=32 time=24ms TTL=61

Ping statistics for 212.69.40.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 24ms, Average = 22ms

Congratulations on your 1000th post and becoming a Master. 

[David]

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

C:\Users\David> ping idnet.net

Pinging Idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms 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 = 39ms, Maximum = 41ms, Average = 40ms

C:\Users\David>

A little high for me

[Rik]

High compared to normal, David?

[Glenn]

mine are 20ms up

[Rik]

How strange. It would suggest a BT issue to me, since all other factors are the same for both of us.

[esh]

I've been seeing nice pings for several days in a row now. Better than they were before in fact. I'm at around 25ms now instead of 40ms. I'll be sure to bore you all with a high-quality diagram when I have the time.

Good job anyway. The high pings were a bit of a nuisance but at least my connection didn't fall into absolute disarray.

[Sebby]

That's good to hear.

[Simon]

It does seem as though things are more or less sorted now, thankfully.

[Lance]

We know when things are going well as the forum gets much quieter!

[Simon]

Yes, rather a shame, that. 

[Rik]

Don't worry, I've got an order in with Simon for a cataclysmic failure later today. 

[Lance]

cataclysmic

One of my favourite words, I must try and get it into my management reports next week!

[Rik]

We could add a few more, if you'd like suggestions.

[Lance]

I'll post a list of previously used words (by myself and colleagues for a laugh) when i'm back in the office. In the context of a financial report some off them are very impressive!

[Rik]

You're on.

[esh]

One of my favourite words, I must try and get it into my management reports next week!

Lucky for you, I'm writing a scientific paper right now on things called cataclysmic variables! I'm sure you can tie that in to your report...uh... somehow.

[Rik]

Probably wrt to the cost of the pension fund. 

[Lance]

Lucky for you, I'm writing a scientific paper right now on things called cataclysmic variables! I'm sure you can tie that in to your report...uh... somehow.

Thanks for the idea!

[esh]

Plot as promised.



I think you can see it's looking pretty good right now. As usual, the reminder is each data point is an average of 144 over the course of the day, which is probably why it "looks" better than it was (most people were reporting 150+ whereas it reads 90 on this plot because it was not constant high pings, mostly).

[Rik]

I'm glad you're getting there. Yesterday, across 10 hours pinging at 10 second intervals, I only recorded 14 pings which exceeded 40ms, the average for the day was 23.5ms.

[esh]

Yeah I am seeing 20ms a lot now. Obviously being a line that serves an office and hosts services I can't expect the lowest pings, but 30ms average over a day is the best I've ever seen a "consumer grade" broadband line. It'll be interesting to give it a few weeks and see how stable we get. I should stress that even with the ping times varying across the board for two weeks I still had all the bandwidth I could handle.

[karser]

Argh after 2 weeks of being back to fairly normal with just the odd router reboot needed its gone crazy again:

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

Reply from 85.236.96.22: bytes=32 time=62ms TTL=124
Reply from 85.236.96.22: bytes=32 time=71ms TTL=124
Reply from 85.236.96.22: bytes=32 time=129ms TTL=124
Reply from 85.236.96.22: bytes=32 time=111ms TTL=124

Ping statistics for 85.236.96.22:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 129ms, Average = 93ms

Tried 4 router reboots now, full 30 mins & everything :s