Ping times Jan 28 onwards

[Rik]

I can't explain that, I'm seeing a 19-27ms range with a 21.5ms average to IDNet and:

ping 85.236.96.22

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=25ms TTL=124
Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=26ms 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 = 24ms, Maximum = 26ms, Average = 24ms

To multiplay. It could be exchange congestion at this time of night, when I spoke to IDNet last, there was no congestion anywhere on their network, ie they have it re-balanced. If it continues, all I can suggest is running a longer ping, either using an app like PingGraph or by adding the -n 100 parameter to the command line, and let support have your results.

[karser]

Seems to have been fine again these last 2 nights thankfully, must have just been a blip, but after 2 or 3 hours of it on saturday I was expecting the worst. The pings were crazy all over btw, I only used multiplay as an example.

[4Way]

Anyone else got poor pings again?

Reply from 212.69.40.3: bytes=32 time=138ms TTL=61
Reply from 212.69.40.3: bytes=32 time=184ms TTL=61
Reply from 212.69.40.3: bytes=32 time=94ms TTL=61
Reply from 212.69.40.3: bytes=32 time=111ms 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 = 94ms, Maximum = 184ms, Average = 131ms

Better start Ping Graph up again. Bugger thought all this was sorted.

[Glenn]

Mine are fine

Pinging 212.69.40.3 with 32 bytes of data:
Reply from 212.69.40.3: bytes=32 time=37ms TTL=61
Reply from 212.69.40.3: bytes=32 time=35ms TTL=61
Reply from 212.69.40.3: bytes=32 time=36ms TTL=61
Reply from 212.69.40.3: bytes=32 time=34ms 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 = 34ms, Maximum = 37ms, Average = 35ms

Have you tried dropping the PPP session or rebooting the router?

[4Way]

Yes, no change at present. I'll turn the router off when I go to bed and see how it is in the morning. Shouldn't have to keep doing this though.

[Lance]

My pings are also fine. The fact that no-one else has yet come here reporting high pings leads me to believe it is a isolated problem to your line, exchange, or virtual path from the exchange. Let us know if it is any better in the morning. 

[juiceuk]

Well my pings went mad a little while ago. I'm getting spikes now. I have been going mad at bf2142 the last week because it keeps stuttering and I was thinking it was graphics related so I have tried different drivers, no change. I finally got around to putting the game back on the old pc and guess what same thing happens. The reason I thought graphics or hardware related was my pings have been in the twenties since the upgrade was sorted out. I think somethings wrong in the network because in multi player fps games when everyone starts warping all over the place it points to network issue. I checked my pings when this was happening but they were ok (low twenties), maybe packet loss of some kind is causing it. I can never catch it with my cmd ping though.

Here is what I mean by spikes

Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    25 ms    25 ms    25 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   210 ms   107 ms    24 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    27 ms    35 ms    30 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    25 ms    24 ms    25 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    27 ms    28 ms    25 ms  www.idnet.net [212.69.36.10]

Trace complete.

Is this asterisk a sign of packet loss?


Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    24 ms    26 ms     *     telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    23 ms    27 ms    24 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    24 ms    26 ms    24 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    30 ms    25 ms    24 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    23 ms    25 ms    24 ms  www.idnet.net [212.69.36.10]

Trace complete.

It was a lot worse earlier.

I forgot I had pingplotter installed. It shows I am getting packet loss too.

[4Way]

Everything Ok tonight, looks like a good nights sleep did the router some good

[Simon]

Glad to hear it, and one is just about to do the same for me. 

[juiceuk]

4way you've given it to me. Its like pass the parcel, lol.

[4Way]

Quick, pass it on to someone else