Pings

AvengerUK · Sep 02, 2006, 17:53:28

That does indeed mean BT are telling porkies

It would say "Fast path" otherwise!

Note: ill run that program of yours when i get home!!

maxping · Sep 02, 2006, 18:00:55

Thanks Avenger at least i now know that when the BT dip s***s finally get round to switching it off for real things will go back to normal.

Its got me so frustrated ive been up to my mothers house today to run a few pings tests from here pc with Virgin broadband.

She gets a average of 37ms , i came away more frustrated

karvala · Sep 02, 2006, 19:33:35

Quote from: AvengerUK on Sep 02, 2006, 17:53:28
That does indeed mean BT are telling porkies

It would say "Fast path" otherwise!

Note: ill run that program of yours when i get home!!

Yeah, exactly. Mine said FAST until I once manually rebooted the router; now it says INTERLEAVED, even more than a week after interleaving was alledgedly switched off, in spite of rebooting numerous times, leaving the router powered off overnight, and even doing a full reset. Grrrrrr....

maxping · Sep 02, 2006, 20:01:13

Keep them coming peeps I'm feeling better by the post

browney · Sep 02, 2006, 20:20:09

Ping statistics for www.idnet.net :
Packets: Sent = 100, Received = 100, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 31ms, Average = 29ms

Ping statistics for www.multiplay.co.uk :
Packets: Sent = 100, Received = 100, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 90ms, Average = 30ms

AvengerUK · Sep 02, 2006, 21:02:40

I have run visual ping with the following results:

(if someone can tidy up this barrage of images..ie get them next to each other or something

!! EDIT: Im AM Clever!!!)

I would also like to note my L8NC Graph...which is currently showing periodic loss

I hate to say it, but im getting really really fed up. Being a heavy gamer, it just simply wont do.

Ive been with many ISP's, some with similar support (good) but with ping problems. Who, led me around in circles until i left. Ive had ISP's ive been happy with! AOL for instance. Its just a problem which some ISP's have, im not saying these ISP's are "bad" - for "normal" users its fine, 100%! - However, for gamers, its difficult.

Any one have any suggestions? - I mean, should i wait in hope? or move on...

maxping · Sep 03, 2006, 11:44:46

Avenger could you line the picture links up one under another to get rid of the "widescreen" look of the thread,thanks.

I have run quite a few tests using visual ping and i do not seem to be getting many spikes it just seems to fluctuate between 50ms and 60ms, if you are getting huge spikes there must be a problem somewhere.

What have CS said about it?

As you can see below my connection is rock solid .

Pinging www.idnet.net with 32 bytes of data:
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:53ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:54ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:53ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:50ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:53ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:52ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:51ms TTL:60
Ping statistics for www.idnet.net :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 54ms, Average = 52ms

equk · Sep 03, 2006, 13:44:18

Quote from: AvengerUK on Sep 02, 2006, 21:02:40
I would also like to note my L8NC Graph...which is currently showing periodic loss

I hate to say it, but im getting really really fed up. Being a heavy gamer, it just simply wont do.

Ive been with many ISP's, some with similar support (good) but with ping problems. Who, led me around in circles until i left. Ive had ISP's ive been happy with! AOL for instance. Its just a problem which some ISP's have, im not saying these ISP's are "bad" - for "normal" users its fine, 100%! - However, for gamers, its difficult.

Any one have any suggestions? - I mean, should i wait in hope? or move on...

I seem to be getting the same, pinging multiplay.co.uk

Seems to ping at 20ms but jumps to 30ms every 5 or so packets.

Code Select

--- core1.multiplay.co.uk ping statistics ---
42 packets transmitted, 42 received, 0% packet loss, time 41242ms
rtt min/avg/max/mdev = 19.757/21.824/30.547/1.941 ms

Would be cool if I could get 16ms but the idnet gateway pings at 20+ms so no chance of that

maxping · Sep 03, 2006, 13:56:21

ECUK can you remove the quote from your post so when Avenger edits his post we will get back to the narrow forum instead of this wide one its a pain to use.

AvengerUK · Sep 03, 2006, 15:48:49

Hmm, someone did it for me?

Anyway, so no one else is getting the results im getting?!

EDIT: As you can see, its again regular & large spikes: http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e

Anyone have any advice? - its killing me! (virtually anyway

)

equk · Sep 03, 2006, 16:09:22

well it was my tenth day yesterday and today the ping times are just as bad, was just on a quake3 server which I've always pinged 26-30ms on before(on my previous isp's)

Today seemed to be 50ms+ and some massive pl aswell as ping going up to 150ms, pinging it on ping command gives me a low of 40ms but totally unstable, I'm probably going to contact support, might try the bttest connection to see what results I get there then I guess I will know if it's my line or the ISP

I feel mislead by the reviews and results on adslguide as idnet were top, but looking on here everyone is getting ping problems

Gilba · Sep 03, 2006, 16:33:29

I think max can be a iffy, especially if you have interleave on.

Idnet have or I think still got a ping issue on one of their routers. I'm not sure if it's been resolved yet.

My fixed rate line seems fine and as I don't play online games anymore I'm to fussed.

Can you give me ip address to the server and I will ping it for a few minutes.

equk · Sep 03, 2006, 16:35:10

The one I was just on - 194.109.69.93

But also have problems to - 85.25.10.49

Code Select

--- 85.25.10.49 ping statistics ---
68 packets transmitted, 67 received, 1% packet loss, time 67418ms
rtt min/avg/max/mdev = 39.574/49.573/86.018/10.686 ms

Gilba · Sep 03, 2006, 16:46:57

194.109.69.93 seems fine to me with low 30ms pings

Ping statistics for 194.109.69.93:
Packets: Sent = 148, Received = 148, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 63ms, Average = 33ms

85.25.10.49 not so good ~40ms ping with the odd spike

Ping statistics for 85.25.10.49:
Packets: Sent = 123, Received = 123, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 90ms, Average = 41ms

maxping · Sep 03, 2006, 17:32:33

QuoteAnyone have any advice? - its killing me! (virtually anyway )

I am also getting spikes but mine probably look worse than they should because they are all starting from 50ms.

Ronnie · Sep 03, 2006, 17:33:34

i am still getting ping spikes at my end as well check out the graph this is only for five min

[attachment deleted by admin]

maxping · Sep 03, 2006, 17:36:39

Whats that you are using to test it ?

Ronnie · Sep 03, 2006, 17:41:42

my latency graph looks like this

[attachment deleted by admin]

Ronnie · Sep 03, 2006, 17:42:08

pingplotter

maxping · Sep 03, 2006, 18:15:59

Quote from: Ronnie on Sep 03, 2006, 17:42:08
pingplotter

Thanks i will go google

maxping · Sep 03, 2006, 18:22:21

If you are using Visual ping you can change the settings at the top to make the pause as long as you want and the loops to whatever you want.

http://www.softpedia.com/get/Network-Tools/Traceroute-Whois-Tools/Visual-Ping.shtml

Try 2000 for the pause you get a far more detailed bar at the bottom. (note the 1 big spike)

Ronnie · Sep 03, 2006, 18:52:26

yip you can configure pingplotter quite a bit good piece of kit

AvengerUK · Sep 03, 2006, 20:08:26

Soo..wounder why my pings went ok for a few hours last weekend...then went bad again!

equk · Sep 04, 2006, 11:13:23

hmm nice traceroute

100+ms to the gateway

Code Select

 1  cisco (192.168.1.1)  1.223 ms  0.685 ms  0.637 ms
 2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  125.693 ms  117.281 ms  117.678 ms
 3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  107.914 ms  98.383 ms  93.925 ms
 4  telehouse-gw.idnet.net (212.69.40.1)  90.003 ms  89.103 ms  83.910 ms

Code Select

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
 1  cisco (192.168.1.1)  0.779 ms  0.668 ms  0.645 ms
 2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  108.783 ms  93.261 ms  89.976 ms
 3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  98.240 ms  92.639 ms  87.906 ms
 4  telehouse-gw.idnet.net (212.69.40.1)  91.981 ms  109.195 ms  109.878 ms
 5  redbus-gw.idnet.net (212.69.63.1)  111.976 ms  103.257 ms  97.914 ms
 6  ams-ix.sara.xs4all.net (195.69.144.48)  109.954 ms  99.307 ms  103.829 ms
 7  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  118.022 ms  125.129 ms  111.875 ms
 8  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  131.988 ms  127.015 ms  131.923 ms
 9  quake3-04.xs4all.nl (194.109.69.93)  109.909 ms  103.716 ms  107.857 ms

Code Select

traceroute to 213.208.119.119 (213.208.119.119), 30 hops max, 40 byte packets
 1  cisco (192.168.1.1)  0.699 ms  0.671 ms  0.648 ms
 2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  102.915 ms  105.200 ms  109.977 ms
 3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  108.048 ms  118.792 ms  127.884 ms
 4  telehouse-gw.idnet.net (212.69.40.1)  115.879 ms  105.198 ms  117.926 ms
 5  g2-2-501.cr01.hx2.bb.pipex.net (193.203.5.14)  126.183 ms  119.658 ms  123.440 ms
 6  v3952.cr05.tn5.bb.pipex.net (62.72.137.9)  98.425 ms  97.610 ms  115.846 ms
 7  g1-1-6.er01.tn5.bb.pipex.net (62.72.140.142)  124.337 ms  113.510 ms  114.001 ms
 8  ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14)  105.883 ms  93.679 ms  87.892 ms
 9  213.208.119.119 (213.208.119.119)  85.629 ms  96.754 ms  101.924 ms

AvengerUK · Sep 04, 2006, 11:43:00

Quote from: equk on Sep 04, 2006, 11:13:23
hmm nice traceroute 100+ms to the gateway

Code Select Expand
1 cisco (192.168.1.1) 1.223 ms 0.685 ms 0.637 ms 2 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 125.693 ms 117.281 ms 117.678 ms 3 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 107.914 ms 98.383 ms 93.925 ms 4 telehouse-gw.idnet.net (212.69.40.1) 90.003 ms 89.103 ms 83.910 ms
Code Select Expand
traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets 1 cisco (192.168.1.1) 0.779 ms 0.668 ms 0.645 ms 2 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 108.783 ms 93.261 ms 89.976 ms 3 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 98.240 ms 92.639 ms 87.906 ms 4 telehouse-gw.idnet.net (212.69.40.1) 91.981 ms 109.195 ms 109.878 ms 5 redbus-gw.idnet.net (212.69.63.1) 111.976 ms 103.257 ms 97.914 ms 6 ams-ix.sara.xs4all.net (195.69.144.48) 109.954 ms 99.307 ms 103.829 ms 7 0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5) 118.022 ms 125.129 ms 111.875 ms 8 0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94) 131.988 ms 127.015 ms 131.923 ms 9 quake3-04.xs4all.nl (194.109.69.93) 109.909 ms 103.716 ms 107.857 ms
Code Select Expand
traceroute to 213.208.119.119 (213.208.119.119), 30 hops max, 40 byte packets 1 cisco (192.168.1.1) 0.699 ms 0.671 ms 0.648 ms 2 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 102.915 ms 105.200 ms 109.977 ms 3 telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45) 108.048 ms 118.792 ms 127.884 ms 4 telehouse-gw.idnet.net (212.69.40.1) 115.879 ms 105.198 ms 117.926 ms 5 g2-2-501.cr01.hx2.bb.pipex.net (193.203.5.14) 126.183 ms 119.658 ms 123.440 ms 6 v3952.cr05.tn5.bb.pipex.net (62.72.137.9) 98.425 ms 97.610 ms 115.846 ms 7 g1-1-6.er01.tn5.bb.pipex.net (62.72.140.142) 124.337 ms 113.510 ms 114.001 ms 8 ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14) 105.883 ms 93.679 ms 87.892 ms 9 213.208.119.119 (213.208.119.119) 85.629 ms 96.754 ms 101.924 ms

I also had a similar issue, which sorted itself about 1hour ago! - started around 9 Am!

Man, im getting sooo tired of this, its coming to the point where it as bad, or worse than my last ISP - and, in their case it was contention, although i cant see it being that here, or atleast not all the time due to the regular spikes!

EDIT: and its a hell of a lot better early morning!