Pings

Jeff · Aug 20, 2006, 00:17:23

The official:

We've been investigating the ping spikes. It's been a curious one and what hasn't helped is that the issue has lacked consistency in that most customers seem to be unaffected. Mostly gamers (and not all of them for sure) seem to be affected for obvious reasons.
Though not yet confirmed, we suspect the route of the cause could be a faulty interface card. We're just waiting now for more data from some intensive debugging reports we've been running and then we should be in a better position to decide on the best solution. The ping spikes are almost certainly caused by the BGP scanner, though this in itself is not unusual and has proven to be a red herring, only the spikes are higher than would be expected which suggests they're the symptom of another issue. All configuration modifications to date have yielded little improvement which is leading us to the conclusion that we have a faulty interface card which may simply require replacing.

We're almost there but we want to be certain before we take the necessary steps to fix.

Any affected, sit tight for a couple of days. If no joy, post here or PM me and I will press for more info

browney · Aug 20, 2006, 01:13:12

Hi, my pings are back down to 27ms which i am happy with buy any less and i would be in amazement

maxping · Aug 20, 2006, 10:37:19

Jeff thanks for the info.

My problem is not the spikes its the fact i can no longer get a low ping under 50 that i always got until a couple of weeks ago.

Is this caused by the problem mentioned in your post and when the spikes issue is fixed the pings will drop?

Bill · Aug 20, 2006, 10:40:09

Yeah, that's what I got from Tim on Friday, I posted the gist of it on the AG board.

Bill · Aug 20, 2006, 10:42:01

Quote from: browney on Aug 20, 2006, 01:13:12
Hi, my pings are back down to 27ms which i am happy with buy any less and i would be in amazement

C:\WINDOWS>tracert idnet.net

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

1 3 ms 1 ms <10 ms 192.168.1.1
2 15 ms 13 ms 14 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 14 ms 14 ms 14 ms telehouse-gw.idnet.net [212.69.40.1]
4 16 ms 14 ms 14 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 19 ms 15 ms 15 ms idnet.net [212.69.36.10]

Trace complete.

mrapoc · Aug 20, 2006, 10:43:43

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

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

Trace complete.

$:-\$

browney · Aug 20, 2006, 11:33:17

VaderDSL · Aug 20, 2006, 12:27:06

Still not 100% but a lot better than it was when I posted a week or so ago.

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

C:\Documents and Settings\Administrator>tracert idnet.net

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

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 16 ms 17 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 113 ms 271 ms 316 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
4 17 ms 17 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
5 17 ms 17 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>tracert idnet.net

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

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 16 ms 16 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 16 ms 16 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
4 16 ms 18 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
5 17 ms 17 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>tracert idnet.net

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

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 16 ms 15 ms 15 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 18 ms 16 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
4 17 ms 18 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
5 16 ms 17 ms 18 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>tracert idnet.net

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

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 16 ms 16 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 17 ms 16 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
4 18 ms 16 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
5 17 ms 17 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>tracert idnet.net

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

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 15 ms 17 ms 16 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 16 ms 17 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
4 17 ms 17 ms 18 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
5 18 ms 17 ms 17 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>

browney · Aug 20, 2006, 14:45:25

I have also seen a massive ping in the 3rd hop sometimes

mrapoc · Aug 20, 2006, 15:43:46

i always get high pings in the 1st

Bill · Aug 20, 2006, 15:57:47

That's your own router !!!

BassoProfundo · Aug 20, 2006, 16:42:27

yeah, I noticed that! His router is taking 199ms to respond to a ping on his lan. Should be virtually instantaneous. Summat wrong there.

maxping · Aug 20, 2006, 17:03:17

Have just been to my brothers who recently changed to Orange BB and i did a ping -t and in 15 mins he got 23ms at the lowest and 35 highest , i wish i hadn't gone to see him now , and the phone he got free is a cracker.

Toxteth_OGrady · Aug 20, 2006, 19:12:15

Quote from: mrapoc on Aug 20, 2006, 15:43:46
i always get high pings in the 1st

Do you have a Speedtouch router? If you do it's a route tracing anomaly and nothing to worry about. Try ping 192.168.1.254 and that will show the true latency to your router.

8)

TOG

mrapoc · Aug 20, 2006, 21:32:58

Tracing route to dsldevice.lan [192.168.1.254]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]

Trace complete.

mrapoc · Aug 20, 2006, 21:34:24

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

1 98 ms 99 ms 199 ms dsldevice.lan [192.168.1.254]
2 24 ms 23 ms 23 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 25 ms 24 ms 24 ms telehouse-gw.idnet.net [212.69.40.1]
4 23 ms 24 ms 24 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 25 ms 24 ms 24 ms 213.228.201.13
6 25 ms 25 ms 30 ms 72.14.238.244
7 46 ms 46 ms 46 ms 216.239.49.254
8 35 ms 34 ms 33 ms 72.14.232.233
9 46 ms 46 ms 45 ms 64.233.174.187
10 47 ms 64 ms 48 ms 64.233.174.14
11 46 ms 44 ms 45 ms 66.102.9.104

Scott · Aug 21, 2006, 07:57:19

Latest from Tim as promised - apologies for not getting it online until now - it went to my work addy !

"..Quick update for you as promised. Though not yet confirmed, we suspect the route of the cause to be a faulty interface card. We're just waiting now for some more data from some intensive debugging reports we've been running and then we should be in a better position to decide on the best solution. "

This was 5:30pm on Friday night so hopefully their continued testing will have thrown up some useful info and we'll hear more as soon as...

maxping · Aug 21, 2006, 18:11:19

Quote from: mrapoc on Aug 20, 2006, 21:34:24
Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 98 ms 99 ms 199 ms dsldevice.lan [192.168.1.254]
2 24 ms 23 ms 23 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 25 ms 24 ms 24 ms telehouse-gw.idnet.net [212.69.40.1]
4 23 ms 24 ms 24 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 25 ms 24 ms 24 ms 213.228.201.13
6 25 ms 25 ms 30 ms 72.14.238.244
7 46 ms 46 ms 46 ms 216.239.49.254
8 35 ms 34 ms 33 ms 72.14.232.233
9 46 ms 46 ms 45 ms 64.233.174.187
10 47 ms 64 ms 48 ms 64.233.174.14
11 46 ms 44 ms 45 ms 66.102.9.104

I can beat that heres my MaxPing

1 * * * Request timed out.
2 49 ms 51 ms 51 ms telehouse-bb-gw1-vpdn.idnet.net [212.69
3 50 ms 50 ms 62 ms telehouse-gw.idnet.net [212.69.40.1]
4 51 ms 51 ms 75 ms rt-lonap-a.thdo.bbc.co.uk [193.203.5.90
5 56 ms 96 ms 188 ms 212.58.238.153
6 51 ms 52 ms 51 ms 212.58.238.157
7 51 ms 53 ms 51 ms www4.rbsov.bbc.co.uk [212.58.227.74]

1 * * * Request timed out.
2 49 ms 49 ms 49 ms telehouse-bb-gw1-vpdn.idnet.net [212.69
3 132 ms 349 ms 307 ms telehouse-gw.idnet.net [212.69.40.1]
4 51 ms 51 ms 49 ms rt-lonap-a.thdo.bbc.co.uk [193.203.5.90
5 66 ms 63 ms 51 ms 212.58.238.153
6 50 ms 53 ms 51 ms 212.58.238.157
7 51 ms 51 ms 51 ms www6.rbsov.bbc.co.uk [212.58.227.76]

AvengerUK · Aug 21, 2006, 21:08:51

Ill do a few traces etc in a sec...im finally at home sitting at my pc! just in time for i28 aswell!, as for how i fixed it...ill copy the post i made at my "Planetside outfit's forums"!

QuoteSorted - kinda,

Basically, the error in the memory is on one stick of DDR400 Dual channel (1GB) - When tested alone, single channel, the error does not show, however when running them together, it does. The error shown is a 4 Bit error on the same address each time. Now, i assumed that this might not matter for the time being, although somethings may and will crash the computer...i dont think planetside and alike will! - why? Basically its down to parity bits. 1 wrong parity bit, then you get your error. But, its 4 error bits, so, the parity bits will cancel each other out - as far as the games concerned its fine, provided that segment of memory is only being read and not written (often, prone to errors) it should be ok.

The error itself is just over 1500mb, so, i dont think planetside will use that much up anyway

Jeff · Aug 21, 2006, 23:12:17

QuoteLatest from Tim as promised

Huh, I get nowt

Me having tha biggest mouth n`all

Bill · Aug 21, 2006, 23:18:18

Quote from: Jeff on Aug 21, 2006, 23:12:17
QuoteLatest from Tim as promised

Huh, I get nowt Me having tha biggest mouth n`all

It's an extract from the same message you posted this morning on the AG forum...

Keep up lad, keep up

Jeff · Aug 21, 2006, 23:24:39

Oh aye, just with Scott getting it today and ... well never mind, bit miffed at not being furnished today as it were.

Big fella is back from his hols today ... was online when I came on but soon buggered off ... he knows I`m gonna be on his case about a few things

*Trying to provoke a response from said big fella*

Aye, keep uz reet Bill

Bill · Aug 21, 2006, 23:31:04

Quote from: Jeff on Aug 21, 2006, 23:24:39
*Trying to provoke a response from said big fella*

Give the man a chance... I've seen him around on AG, no doubt he's catching up on whatever subversion he thinks we might be planning

Jeff · Aug 21, 2006, 23:39:16

Aye, whey, it`s tough at the top

Simon_idnet · Aug 22, 2006, 10:53:05

Hi Guys

Two weeks is a hell of a long time! It took me from 08:30 to 23:00 just to read, only reading, emails and forum posts! I was of cross-eyed and crooked-back by the end

On the ping-spike thing. We can see it but we don't know what is causing it. We have had Cisco looking into it too and some outside consultants.

We are treating it as high priority even though it only affects ICMP packets. TCP packets are unaffected.

More when we know it.
Cheers
Simon