Pings again and again and again

Started by spiral, Mar 10, 2007, 08:17:02

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

spiral

Mar 10, 2007, 08:17:02
What is going on with pings this morning, i go for a quick game of battlefield 2142 and my pings are 160 i ping the bbc pings of 13. But i do a tracert to www.idnet.net and get this.


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

  1    67 ms    99 ms    99 ms  speedtouch.lan [192.168.1.1]
  2    13 ms    13 ms    13 ms  telehouse-gw3-msdp.idnet.net [212.69.63.51]
  3    15 ms    14 ms    14 ms  redbus-gw.idnet.net [212.69.63.1]
  4    14 ms    14 ms     *     www.idnet.net [212.69.36.10]
  5    17 ms  3384 ms    12 ms  www.idnet.net [212.69.36.10]

Trace complete.

I have to say i'm getting bored of this now speeds are top notch again and i'm glad but i would like to be able to have a quick game ocasionally too.




If you keep repeating a lie, keep repeating a lie for long enough it will become truth.

zulu26

#1
Mar 10, 2007, 09:21:15
According those results the problems lies at your router your end.
All the pings out side you network look very good.

siege2

#2
Mar 10, 2007, 09:28:58
I get using tracert for www.idnet.net

1    <1 ms    <1 ms    <1 ms  192.168.0.1
2    30 ms    35 ms    29 ms  telehouse-gw3-msdp.idnet.net [212.69.63.51]
3    30 ms    33 ms    31 ms  redbus-gw.idnet.net [212.69.63.1]
4    33 ms    31 ms    29 ms  www.idnet.net [212.69.36.10]

ping off average 30 ms is the norm, maybe that it is I do not live near anough to my isp way down south.

when I play Unreal Tournament I get a ping off 16 ms
Home SuperMax "BT IPStream Max Premium"

_____________Downstream____Upstream
Data rate...........8128.....................832
Noise margin.....8.1  ......................12.0
Output power....7.8.......................12.5
Attenuation........4.0.......................2.0

siege2

#3
Mar 10, 2007, 09:34:59
"Well the change over gone to plan and at the time said so that all good.
Download speed as dropped down to 2mb, I'm hoping that just to with the line relearning its speed and will go back up to whats it was.
Uploads gone up to 650k so thats doubled my upload speed."


Zulu26 phone IDnet on Monday tell them your profile is 2meg get them to contact BT to get it properly set
Home SuperMax "BT IPStream Max Premium"

_____________Downstream____Upstream
Data rate...........8128.....................832
Noise margin.....8.1  ......................12.0
Output power....7.8.......................12.5
Attenuation........4.0.......................2.0

rireed3

#4
Mar 10, 2007, 09:52:46
from spiral

Quote
  1    67 ms    99 ms    99 ms  speedtouch.lan [192.168.1.1]
  2    13 ms    13 ms    13 ms  telehouse-gw3-msdp.idnet.net [212.69.63.51]
  3    15 ms    14 ms    14 ms  redbus-gw.idnet.net [212.69.63.1]
  4    14 ms    14 ms     *     www.idnet.net [212.69.36.10]
  5    17 ms  3384 ms    12 ms  www.idnet.net [212.69.36.10]

and zulu26

Quote
...the problems lies at your router your end.

That 67 or 99 ms to the router is an artifact of Speedtouch routers.  I've had three and they all do that on tracert.  It never affects the downstream pings, and if I do a 'ping speedtouch.lan' I get

Quote
Reply from xxx.xxx.xxx.xxx: bytes=32 time=1ms TTL=64
Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=64
Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=64
Reply from xxx.xxx.xxx.xxx: bytes=32 time<10ms TTL=64

I think spiral is worried about the 'no return' in hop 4 and the 3 seconds in one try of the last hop.

Richard

AvengerUK

#5
Mar 10, 2007, 10:45:51
Spiral - the speedtouch routers will always show a high ping on traceroutes, ive no idea why, but they always do!

use the ping command to find your true ping ;)

Rik

#6
Mar 10, 2007, 11:41:39
Quote from: AvengerUK on Mar 10, 2007, 10:45:51
Spiral - the speedtouch routers will always show a high ping on traceroutes, ive no idea why, but they always do!

Because they can? :)

Thanks for that info, Avenger - always useful to know of these quirks (like Netgear routers gradually dropping the indicated noise margin).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

spiral

#7
Mar 10, 2007, 11:52:11
Thanks for the info guys seems to have settled now.

Back to my usual 20+ pings in Battlefield.  :)
If you keep repeating a lie, keep repeating a lie for long enough it will become truth.

Rik

#8
Mar 10, 2007, 11:54:26
Glad to hear it, Spiral. Perhaps your connection was just so excited at being here it was having a little party? ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Wingco1

#9
Mar 14, 2007, 21:55:18
Remember that Ping spike? it seems to be back :o

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>ping 212.69.63.1 -t

Pinging 212.69.63.1 with 32 bytes of data:

Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=39ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=434ms TTL=253
Reply from 212.69.63.1: bytes=32 time=159ms TTL=253
Reply from 212.69.63.1: bytes=32 time=190ms TTL=253
Reply from 212.69.63.1: bytes=32 time=278ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=107ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=84ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=84ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=56ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=85ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=85ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=84ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=85ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=85ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=140ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=71ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=200ms TTL=253
Reply from 212.69.63.1: bytes=32 time=276ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=97ms TTL=253
Reply from 212.69.63.1: bytes=32 time=182ms TTL=253
Reply from 212.69.63.1: bytes=32 time=138ms TTL=253
Reply from 212.69.63.1: bytes=32 time=49ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=85ms TTL=253
Reply from 212.69.63.1: bytes=32 time=38ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=56ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=35ms TTL=253
Reply from 212.69.63.1: bytes=32 time=84ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=145ms TTL=253
Reply from 212.69.63.1: bytes=32 time=37ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253
Reply from 212.69.63.1: bytes=32 time=36ms TTL=253

Ping statistics for 212.69.63.1:
    Packets: Sent = 101, Received = 101, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 434ms, Average = 60ms

Gilba

#10
Mar 14, 2007, 23:07:57
I don't think it matters that much. All it means is that the router took a bit longer to respond the ping request its the pings after the router that matter.

Example

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\tommy>tracert www.idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    16 ms    16 ms    16 ms  telehouse-gw3-msdp.idnet.net [212.69.63.51]
  3    15 ms    16 ms    16 ms  redbus-gw.idnet.net [212.69.63.1]
  4    19 ms    16 ms    17 ms  www.idnet.net [212.69.36.10]

Trace complete.

As you can see trace goes through redbus router. and as you can see below the pings are ok.

C:\Documents and Settings\tommy>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=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=17ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=17ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=14ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61
Reply from 212.69.36.10: bytes=32 time=15ms TTL=61
Reply from 212.69.36.10: bytes=32 time=16ms TTL=61

Ping statistics for 212.69.36.10:
    Packets: Sent = 33, Received = 33, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 17ms, Average = 15ms

Yet if I ping the router I get the increased pings.

C:\Documents and Settings\tommy>ping 212.69.63.1 -t

Pinging 212.69.63.1 with 32 bytes of data:

Reply from 212.69.63.1: bytes=32 time=14ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=17ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=17ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=18ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=19ms TTL=253
Reply from 212.69.63.1: bytes=32 time=17ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=329ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=282ms TTL=253
Reply from 212.69.63.1: bytes=32 time=375ms TTL=253
Reply from 212.69.63.1: bytes=32 time=110ms TTL=253
Reply from 212.69.63.1: bytes=32 time=162ms TTL=253
Reply from 212.69.63.1: bytes=32 time=262ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253
Reply from 212.69.63.1: bytes=32 time=16ms TTL=253
Reply from 212.69.63.1: bytes=32 time=15ms TTL=253

Ping statistics for 212.69.63.1:
    Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 375ms, Average = 54ms

AvengerUK

#11
Mar 15, 2007, 11:10:24 Last Edit: Mar 15, 2007, 11:12:36 by AvengerUK
your router wont effect Pings if it is functioning correctly. Routers DO fluctuate, but since when does <1ms, going at most to 2ms on very rare occasions going to cause ping spikes?

I am also seeing these spikes again, well, acutally im seeing periods of high pings again recently not that it bothers me!

EDIT: WHOOPS!!! misread your post!!!!! Yes, the redbus router does fluctuate as pings to those routers treat pings as low prioritory - they will fluctuate. I was on about "pings in general" above!!!!
Print
Go Up Pages1
User actions