Woah there ping!

VaderDSL · Aug 08, 2006, 12:17:12

Bit of a ping problem

[mod]Linky url error fixed[/mod]

AvengerUK · Aug 08, 2006, 13:01:14

No problems down my end :/

oh, while on the subject on pings has anyone else noticed that occasionally the 2nd or 3rd hop (which is idnet) sometimes has pings of over 200ms?

spiral · Aug 08, 2006, 13:10:44

Try rebooting your router when this happens, as that has always cleared it for me.

Tis a bit of a pain though.

VaderDSL · Aug 08, 2006, 13:40:41

Restarted numerous times

spiral · Aug 08, 2006, 13:58:31

Oh not good then, have you phoned them?

VaderDSL · Aug 08, 2006, 14:00:44

Yup, spoke to a nice woman who said she'd look into it and told me to watch this space. There's someone else over at ADSLguide having problems.

Yet at the same time there are people not suffering from any high pings whatsover. Probably our local exchange got run over by a bus or something.

spiral · Aug 08, 2006, 14:13:13

Yea maybe or maybe we are on different parts of the network, although i don't know how big Idnets network is.

I know when i was on F2S there were problems for some on different gateways. Something like that anyway.

But you can rest assured that the people at idnet will be working on finding and solving the course of your problem.

mrapoc · Aug 08, 2006, 14:14:27

I have had big problems the last week with high pings!!! I was getting 80 -140 whereas my friends were getting 20 - 30

Dude?

mrapoc · Aug 08, 2006, 14:17:32

QuoteC:\Documents and Settings\James Family>tracert www.idnet.net

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

1 195 ms 199 ms 199 ms dsldevice.lan [192.168.1.254]
2 135 ms 135 ms 122 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 102 ms 100 ms 115 ms telehouse-gw.idnet.net [212.69.40.1]
4 228 ms 271 ms 262 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 161 ms 168 ms 163 ms www.idnet.net [212.69.36.10]

Trace complete.

QuoteC:\Documents and Settings\James Family>tracert www.idnet.net

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

1 115 ms 199 ms 199 ms dsldevice.lan [192.168.1.254]
2 163 ms 152 ms 135 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 136 ms 144 ms 149 ms telehouse-gw.idnet.net [212.69.40.1]
4 162 ms 141 ms 133 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 157 ms 150 ms 148 ms www.idnet.net [212.69.36.10]

Trace complete.

QuoteC:\Documents and Settings\James Family>tracert www.idnet.net

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

1 88 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 124 ms 128 ms 126 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 127 ms 134 ms 132 ms telehouse-gw.idnet.net [212.69.40.1]
4 163 ms 159 ms 173 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 155 ms 158 ms 160 ms www.idnet.net [212.69.36.10]

Trace complete.

hmmmm

QuoteC:\Documents and Settings\James Family>tracert www.google.co.uk

Tracing route to www.l.google.com [66.102.9.147]
over a maximum of 30 hops:

1 71 ms 199 ms 199 ms dsldevice.lan [192.168.1.254]
2 144 ms 142 ms 153 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 115 ms 108 ms 99 ms telehouse-gw.idnet.net [212.69.40.1]
4 79 ms 76 ms 75 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 102 ms 109 ms 116 ms 213.228.201.13
6 169 ms 142 ms 143 ms 72.14.238.244
7 171 ms 186 ms 175 ms 216.239.49.254
8 172 ms 158 ms 125 ms 64.233.174.113
9 134 ms 141 ms 143 ms 72.14.232.239
10 160 ms 158 ms 169 ms 64.233.174.14
11 177 ms 168 ms 174 ms 66.102.9.147

Trace complete.

AvengerUK · Aug 08, 2006, 14:54:06

QuotePinging telehouse-gw.idnet.net [212.69.63.40] with 32 bytes of data:

Reply from 212.69.63.40: bytes=32 time=219ms TTL=253
Reply from 212.69.63.40: bytes=32 time=145ms TTL=253
Reply from 212.69.63.40: bytes=32 time=175ms TTL=253
Reply from 212.69.63.40: bytes=32 time=78ms TTL=253

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

ALWAYS congestion here, not to that extent though:

Quotetracert multiplay.co.uk

Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mygateway1.ar7 [192.168.1.1]
2 20 ms 17 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 244 ms 133 ms 19 ms telehouse-gw.idnet.net [212.69.40.1]
4 24 ms 26 ms 24 ms lonap2.enta.net [193.203.5.135]
5 18 ms 19 ms 19 ms redbus-sov3.core.enta.net [84.45.193.206]
6 19 ms 16 ms 17 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
7 19 ms 22 ms 24 ms multiplay.co.uk [85.236.96.22]

Trace complete.

I hope IDnet sort it

L8NC graph shows vairying pings - i think its because of the hop i highlighted!
http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e

mrapoc · Aug 08, 2006, 17:00:05

got bad pings again while gaming

maxping · Aug 08, 2006, 18:02:15

I have also noticed my pings seem to have increased form the rock steady 40 - 50 to 50 - 65 gaming.

I haven't changed anything this end so wonder whats causing it.

Scott · Aug 08, 2006, 21:29:48

Quote from: maxping on Aug 08, 2006, 18:02:15
I haven't changed anything this end so wonder whats causing it.

One of the BT hamsters ("errol" I believe) caught a nasty sniffle last week so it's little wonder pings have gone up mate

Jeff · Aug 08, 2006, 21:35:03

OK here, 32ms to IDNet.

Are they worse in an evening, daytime? Tried plugging into the test socket etc

AvengerUK · Aug 08, 2006, 21:52:49

For me, the problem is simply with the "telehouse-gw.idnet.net" hop. Occasionally, ie every 3 pings(or less) ill get 200ms or more which has a drastic effect on gaming. Im testing it from the AOL broadband connection im using atm, and im getting the same results. - Congestion?!

Jeff · Aug 08, 2006, 21:57:39

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

C:\Documents and Settings\Jeff>tracert multiplay.co.uk

Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms mygateway.ar7 [192.168.0.1]
2 35 ms 33 ms 33 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 34 ms 35 ms 34 ms telehouse-gw.idnet.net [212.69.40.1]
4 37 ms 41 ms 34 ms lonap2.enta.net [193.203.5.135]
5 36 ms 35 ms 36 ms redbus-sov3.core.enta.net [84.45.193.206]
6 37 ms 35 ms 35 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
7 35 ms 35 ms 35 ms multiplay.co.uk [85.236.96.22]

Trace complete.

Again, OK this end ... pings are usually an individual thing anyway, beetr have a word with CS tomorrow if it becomes too bad :\

Jeff · Aug 08, 2006, 22:32:25

BTW, you can ask CS to turn interleaving off which will improve pings.

VaderDSL · Aug 08, 2006, 23:21:32

I'll ring up tomorrow and ask to have interleaving turned off cheers, although I am not sure interleaving is enabled ... it was definitely a central problem. Lots of people have had problems and I've struggled all day to ping local UK servers at less than 120ms.

It sorted itself out late afternoon however.

maxping · Aug 09, 2006, 01:11:08

Quote from: maxping on Aug 08, 2006, 18:02:15
I have also noticed my pings seem to have increased form the rock steady 40 - 50 to 50 - 65 gaming.

I haven't changed anything this end so wonder whats causing it.

Ive just grabbed a screen to prove my point , the minimum ping used to start approx 40

karvala · Aug 09, 2006, 02:58:04

Quote from: AvengerUK on Aug 08, 2006, 21:52:49
For me, the problem is simply with the "telehouse-gw.idnet.net" hop. Occasionally, ie every 3 pings(or less) ill get 200ms or more which has a drastic effect on gaming. Im testing it from the AOL broadband connection im using atm, and im getting the same results. - Congestion?!

Yeah, exactly the same here. The majority of the time it's okay (in fact my pings are generally very good), but sometimes on that same hop it suddenly spikes at over 200ms, for no obvious reason.

AvengerUK · Aug 09, 2006, 10:39:43

Quote
Pinging telehouse-gw.idnet.net [212.69.63.40] with 32 bytes of data:

Reply from 212.69.63.40: bytes=32 time=20ms TTL=247
Reply from 212.69.63.40: bytes=32 time=56ms TTL=247
Reply from 212.69.63.40: bytes=32 time=274ms TTL=247
Reply from 212.69.63.40: bytes=32 time=165ms TTL=247

*sigh*

mrapoc · Aug 09, 2006, 10:42:16

results after leaving router off overnight again.

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

C:\Documents and Settings\James Family>tracert multiplay.co.uk

Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

1 161 ms 199 ms 99 ms dsldevice.lan [192.168.1.254]
2 23 ms 28 ms 26 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 23 ms 23 ms 41 ms telehouse-gw.idnet.net [212.69.40.1]
4 34 ms 27 ms 23 ms lonap2.enta.net [193.203.5.135]
5 23 ms 23 ms 23 ms redbus-sov3.core.enta.net [84.45.193.206]
6 23 ms 23 ms 23 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
7 24 ms 24 ms 23 ms www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Documents and Settings\James Family>tracert idnet.net

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

1 117 ms 199 ms 100 ms dsldevice.lan [192.168.1.254]
2 23 ms 22 ms 21 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 22 ms 22 ms 23 ms telehouse-gw.idnet.net [212.69.40.1]
4 25 ms 23 ms 23 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 23 ms 23 ms 24 ms www.idnet.net [212.69.36.10]

Trace complete.

AvengerUK · Aug 09, 2006, 11:55:42

So not fixed?

VaderDSL · Aug 09, 2006, 13:50:14

Quote from: mrapoc on Aug 09, 2006, 10:42:16
results after leaving router off overnight again.
QuoteMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\James Family>tracert multiplay.co.uk

Tracing route to multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

1 161 ms 199 ms 99 ms dsldevice.lan [192.168.1.254]
2 23 ms 28 ms 26 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 23 ms 23 ms 41 ms telehouse-gw.idnet.net [212.69.40.1]
4 34 ms 27 ms 23 ms lonap2.enta.net [193.203.5.135]
5 23 ms 23 ms 23 ms redbus-sov3.core.enta.net [84.45.193.206]
6 23 ms 23 ms 23 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
7 24 ms 24 ms 23 ms www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Documents and Settings\James Family>tracert idnet.net

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

1 117 ms 199 ms 100 ms dsldevice.lan [192.168.1.254]
2 23 ms 22 ms 21 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 22 ms 22 ms 23 ms telehouse-gw.idnet.net [212.69.40.1]
4 25 ms 23 ms 23 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 23 ms 23 ms 24 ms www.idnet.net [212.69.36.10]

Trace complete.

it looks like your router there is pinging over 100ms ... unless I am mistaken

karvala · Aug 09, 2006, 13:58:28

Here's an example of the specific problem. First trace:-

Tracing route to www.bbc.net.uk [212.58.224.84]
over a maximum of 30 hops:

1 * * * Request timed out.
2 27 ms 22 ms 36 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 23 ms 20 ms 21 ms telehouse-gw.idnet.net [212.69.40.1]
4 19 ms 20 ms 20 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 26 ms 24 ms 28 ms 212.58.238.149
6 42 ms 38 ms 37 ms www54.thdo.bbc.co.uk [212.58.224.84]

No problem there. Then literally five seconds later:-

Tracing route to www.bbc.net.uk [212.58.224.84]
over a maximum of 30 hops:

1 * * * Request timed out.
2 20 ms 20 ms 21 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 157 ms 314 ms 271 ms telehouse-gw.idnet.net [212.69.40.1]
4 31 ms 30 ms 31 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 28 ms 22 ms 22 ms 212.58.238.149
6 29 ms 27 ms 26 ms www54.thdo.bbc.co.uk [212.58.224.84]

I'm not an online gamer, so it's not really a big deal to me, but problably something the tech guys should be aware of, especially as it is intermittent and seemingly rather random.