Woah there ping!

[VaderDSL]

Bit of a ping problem

[mod]Linky url error fixed[/mod]

[AvengerUK]

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]

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

Tis a bit of a pain though.

[VaderDSL]

Restarted numerous times

[spiral]

Oh not good then, have you phoned them?

[VaderDSL]

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]

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]

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]

C:\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.

C:\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.

C:\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

C:\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]

Pinging 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:

tracert 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]

got bad pings again while gaming 

[maxping]

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]

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]

OK here, 32ms to IDNet.

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

[AvengerUK]

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]

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]

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

[VaderDSL]

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]

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]

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]

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]

results after leaving router off overnight again.

Microsoft 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]

So not fixed?

[VaderDSL]

results after leaving router off overnight again.

Microsoft 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]

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.

[AvengerUK]

Out of interest, has anyone spoken/emailed support about this?

As karvala says, it doesent matter as much to those that dont do alot of online gaming, however those that do it is hell!

[thetrevone]

Karvala, I have noticed I get the odd times when I tracert idnet I get 300 ms reading where it is normally 24ms,  as I write I have a max speed of 250k on my 8mb sync line I know that I will have to do BT speed test to prove what's going on, but I did a reverse traceroute to giganews with the following results with no firewall on, anybody got a clue what this result indicates
Regards
Doug


news.giganews.com
1 gw-vlan201.dca.giganews.com (216.196.98.1) 0 ms 0 ms 0 ms
2 g3-16.gw2.dca.giganews.com (216.196.96.61) 0 ms 0 ms 0 ms
3 217.6.48.249 (217.6.48.249) 0 ms 1 ms 0 ms
4 linx-gw12.LON.GB.net.DTAG.DE (62.154.15.154) 73 ms 73 ms 73 ms
5 62.156.139.142 (62.156.139.142) 74 ms 74 ms 74 ms
6 sl-gw21-lon-1-1.sprintlink.net (213.206.128.102) 74 ms 74 ms 74 ms
7 idnet-b-1.arbinet.net (213.232.65.101) 73 ms 73 ms 73 ms
8 telehouse-bb-gw5.idnet.net (212.69.40.11) 76 ms 74 ms 73 ms
9 * * *
10 * * *
11 * * *
Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com
1 216-196-110-1.ams.giganews.com (216.196.110.1) 0 ms 1 ms 0 ms
2 ams-ix-gw.idnet.net.uk (195.69.144.141) 42 ms 40 ms 48 ms
3 telehouse-gw-fa0-0-1003.idnet.net (212.69.63.2) 364 ms 359 ms 322 ms
4 telehouse-bb-gw5.idnet.net (212.69.40.11) 37 ms 44 ms 49 ms
5 * * *
6 * * *
7 * * *
Max number of unresponsive hops reached (firewall or filter?)

[mrapoc]

i have contacted support but no reply as of yet - got any ideas jeff?

[Glenn]

I get the following from a 212.69.52.xxx address, the results look fine to me, are the people that are getting the bad results on a different IP range?

Tracing route to news.giganews.com [216.196.109.144]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.0.1
  2    14 ms    13 ms    13 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    14 ms    13 ms    14 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    15 ms    14 ms    14 ms  ge2-2.fr1.lon.llnw.net [193.203.5.68]
  5    20 ms    16 ms    15 ms  ag1-6-1.ar1.lon.llnw.net [68.142.84.230]
  6    23 ms    23 ms    25 ms  agg1-15-2-4xoc48.ar1.ams.llnw.net [69.28.172.90]

  7    32 ms    34 ms    33 ms  tge6-2.fr1.ams.llnw.net [69.28.172.85]
  8    38 ms    25 ms    22 ms  giganews.ve212.fr1.ams.llnw.net [87.248.196.14]

  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *


Pinging news.giganews.com [216.196.109.144] with 32 bytes of data:

Reply from 216.196.109.144: bytes=32 time=22ms TTL=115
Reply from 216.196.109.144: bytes=32 time=27ms TTL=115
Reply from 216.196.109.144: bytes=32 time=21ms TTL=115
Reply from 216.196.109.144: bytes=32 time=22ms TTL=115

Ping statistics for 216.196.109.144:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 27ms, Average = 23ms

[karvala]

I get the following from a 212.69.52.xxx address, the results look fine to me, are the people that are getting the bad results on a different IP range?

Mine is from a 212.69.58.xxx address.  You'll need to do at least half a dozen tracerts  to be sure that you're not experiencing the problem; as I mentioned, it's intermittent and only appears in one of every three or four tracerts done.

[AvengerUK]

Mine is from a 212.69.56.xxx address, and i get the problem almost every trace

[Glenn]

I have just run 10 tracert's to news.giganews.com and the highest ping I received was 38ms.

Pinging the same address for approx 2 mins I was averaging 24ms with a peak of 89ms

[AvengerUK]

I have just run 10 tracert's to news.giganews.com and the highest ping I received was 38ms.

Pinging the same address for approx 2 mins I was averaging 24ms with a peak of 89ms

its not the end address were interested in tho....try pinging "telewest-gw.idnet.net"

[karvala]

Well here's an interesting update.  I SSH'd into a Unix machine at work, which obviously means that any internet-related activities that are run from that shell operate through their internet connection, not from my IDNet connection.  While I was there, I thought it would be interesting to ping the suspect router (212.69.40.1), to see whether or not I would see the same pattern, and sure enough look at this:-

64 bytes from 212.69.40.1: icmp_seq=0 ttl=245 time=4.50 ms
64 bytes from 212.69.40.1: icmp_seq=1 ttl=245 time=4.55 ms
64 bytes from 212.69.40.1: icmp_seq=2 ttl=245 time=4.85 ms
64 bytes from 212.69.40.1: icmp_seq=3 ttl=245 time=4.72 ms
64 bytes from 212.69.40.1: icmp_seq=4 ttl=245 time=10.1 ms
64 bytes from 212.69.40.1: icmp_seq=5 ttl=245 time=4.76 ms
64 bytes from 212.69.40.1: icmp_seq=6 ttl=245 time=12.7 ms
64 bytes from 212.69.40.1: icmp_seq=7 ttl=245 time=4.25 ms
64 bytes from 212.69.40.1: icmp_seq=8 ttl=245 time=125 ms
64 bytes from 212.69.40.1: icmp_seq=9 ttl=245 time=257 ms
64 bytes from 212.69.40.1: icmp_seq=10 ttl=245 time=100 ms
64 bytes from 212.69.40.1: icmp_seq=11 ttl=245 time=260 ms
64 bytes from 212.69.40.1: icmp_seq=12 ttl=245 time=4.53 ms
64 bytes from 212.69.40.1: icmp_seq=13 ttl=245 time=174 ms
64 bytes from 212.69.40.1: icmp_seq=14 ttl=245 time=4.57 ms
64 bytes from 212.69.40.1: icmp_seq=15 ttl=245 time=4.31 ms
64 bytes from 212.69.40.1: icmp_seq=16 ttl=245 time=4.53 ms
64 bytes from 212.69.40.1: icmp_seq=17 ttl=245 time=4.27 ms
64 bytes from 212.69.40.1: icmp_seq=18 ttl=245 time=4.41 ms
64 bytes from 212.69.40.1: icmp_seq=19 ttl=245 time=4.34 ms
64 bytes from 212.69.40.1: icmp_seq=20 ttl=245 time=4.69 ms


It seems that the problem is definitely related to something periodically happening on that router, rather than any particular problem with our IDNet connections per se.

[Scott]

<snip!>
It seems that the problem is definitely related to something periodically happening on that router, rather than any particular problem with our IDNet connections per se.

Well done Karvala...excellent detective work - hopefully this is additional background to help IDNet team in their investigations.

[AvengerUK]

Hmm, hadnt thought about that!

THe below pings are from my server farm @ Merdian gate - the ping time is 1ms between them and idnet.  Ive taken pings from one dorment box, i can guarantee that the pings are not affected by anything on my network

box:

Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=106ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=2ms TTL=248

and again:

Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=192ms TTL=248
Reply from 212.69.63.40: bytes=32 time=188ms TTL=248
Reply from 212.69.63.40: bytes=32 time=196ms TTL=248
Reply from 212.69.63.40: bytes=32 time=159ms TTL=248
Reply from 212.69.63.40: bytes=32 time=61ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=1ms TTL=248
Reply from 212.69.63.40: bytes=32 time=384ms TTL=248

[Scott]

[crossposted on AG too]
Just had an update on these telehouse-gw.idnet.net 'goings-on' from Tim Davies of IDNet.
"...have an engineer investigating right now and will report back as soon as they know more"

[karvala]

Sounds promising; thanks for letting us know.

[AvengerUK]

Ditto ^^

[mrapoc]

  Yesh ty v much

[VaderDSL]

Sigh ... wonder if this will be the second ISP I migrate from this month

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   133 ms   138 ms   151 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   117 ms   115 ms   124 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
  4   144 ms   132 ms   118 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
  5   134 ms   129 ms   120 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    98 ms    98 ms    93 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   145 ms   141 ms   136 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
  4   129 ms   128 ms   108 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
  5   137 ms   143 ms   137 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   123 ms   131 ms   138 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   154 ms   151 ms   156 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
  4   103 ms   103 ms   107 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
  5   144 ms   148 ms   138 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   111 ms   119 ms   122 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   132 ms   124 ms   125 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.40.1]
  4   139 ms   152 ms   152 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.1]
  5   130 ms   126 ms   112 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Administrator>

[AvengerUK]

  - I think idnet will sort it out soon enough...if not...im rather stuck anyway! ive been to all the others atleast once!!!!!

[Scott]

[cross-posted to AG - 'Huge Pings']

Further to Tim's update yesterday:

"...no news as yet. The engineer is running more tests today. So far it seems all the obvious possible causes have been ruled out. Next set of diagnostics may take a day or two to complete before we find what we're looking for. For sure as soon as we know more we'll keep you posted."

Thanks to Tim for the update and let's keep all appendages crossed this gets resolved asap.

[Scott]

Sigh ... wonder if this will be the second ISP I migrate from this month

Think that's a little premature Vader...let's get all the facts in and see where we stand. It could simply be a hardware issue, fouled-up routing...who knows. Don't put yourself through all the hassle over something that may be a simple fix.

[mrapoc]

just sit tight  my connection is somewhat improving again although i am still getting a couple of connection errors knocking me off msn/xfire/game servers

[VaderDSL]

Aye, I'll stick it out .. just annoying ... I came from University, where before I had 2 years with Nildram where the service was just top notch ... when I went to University, was on an 8mb JANET connection which was amazing also.

Now leave University Halls and into a house, and resubscribe with Nildram in the middle of July to be greeted with an unusable connection ... insanely high pings over Telia peering (my housemate plays Enemy Down tournaments so this was clearly an unnacceptable situation) and I play Eve Online, and high pings were also a problem.

We migrated over to IDNEt on the 3rd August and started seeing high pings still ... I apologise for my outburst, just I never knew broadband had gone downhill so much in the last year

[Richdog]

Aye, I'll stick it out .. just annoying ... I came from University, where before I had 2 years with Nildram where the service was just top notch ... when I went to University, was on an 8mb JANET connection which was amazing also.

Now leave University Halls and into a house, and resubscribe with Nildram in the middle of July to be greeted with an unusable connection ... insanely high pings over Telia peering (my housemate plays Enemy Down tournaments so this was clearly an unnacceptable situation) and I play Eve Online, and high pings were also a problem.

We migrated over to IDNEt on the 3rd August and started seeing high pings still ... I apologise for my outburst, just I never knew broadband had gone downhill so much in the last year

Are you on MAX mate?  May be worth thinking about down(up?)grading to 2MB IPstream.

[VaderDSL]

Aye on maxDSL ... you think downgrading may help? I have good line stats on maxDSL atm though, high SnR, low Att and full sync

[Richdog]

Aye on maxDSL ... you think downgrading may help? I have good line stats on maxDSL atm though, high SnR, low Att and full sync

Max is riddled with problems... and many prefer the rock-like stability and consistent speeds that standard 2MB IPstream offers. It's the best for gaming and would be a good idea until they sort out the problems with MAX in my opinion.

[VaderDSL]

Cool, I'll call a house meeting this evening ... and see what the consensus is ... going down to a 2Mb IPstream, won't that still be over the same network as maxDSL? I though dropping down would be good if suffering from disconects, or low speeds etc.?

[Richdog]

Cool, I'll call a house meeting this evening ... and see what the consensus is ... going down to a 2Mb IPstream, won't that still be over the same network as maxDSL? I though dropping down would be good if suffering from disconects, or low speeds etc.?

Put it this way, my pings with Virgin 1MB Ipstream were low as hell until the very moment I switched to MAX ADSL... now they er... suck.

Spoke to Miriam this morning and she said she may put me back down to 1MB IPstream to solve the problems i'm having at the moment... then possibly re-enable my MAX ADSL to re-train it as my profile is currently locked at 0.5MB.

Also fitting the ADSL faceplate etc tommorrow so will see what difference this makes to my line. *sigh*

[VaderDSL]

Sorry to hear about all your problems trust the UK to roll out a telecommunications package that hasn't been tested or have the infrastructure to cope

[AvengerUK]

My MAX Profile is currently stuck, and has been for god knows how long. If IDnet could implement a 1Mb IPstream package for me, i would. Annoying thing is tho, without MAX, my highest speed according to BT is 512kb, and i dont think idnet can go against this?

[Richdog]

My MAX Profile is currently stuck, and has been for god knows how long. If IDnet could implement a 1Mb IPstream package for me, i would. Annoying thing is tho, without MAX, my highest speed according to BT is 512kb, and i dont think idnet can go against this?

What are your line stats buddy?

[AvengerUK]

Connection Status           Connected
Us Rate (Kbps)         448
Ds Rate (Kbps)         1856
US Margin         18
DS Margin         6
Trained Modulation         GDMT
LOS Errors         0
DS Line Attenuation         62
US Line Attenuation         31
Peak Cell Rate         1056 cells per sec
CRC Rx Fast         1164
CRC Tx Fast         8
CRC Rx Interleaved         0
CRC Tx Interleaved         0
Path Mode         Fast Path

[Richdog]

Hmm your stats are only marginally worse than mine and I had 1MB no problem...

[AvengerUK]

Hmm your stats are only marginally worse than mine and I had 1MB no problem...

Hmmm, i suppose i might aswell ask support about it - I may still try a differnt router first tho, one which might help a long line

[Jeff]

Your DS margin ... is that steady at 6 or does it drop, particularly at night?

[Richdog]

Oddly enough (I know the Q wasn't directed at me) mine is a constant 6.6 all the time... and even more oddly enough my downstream attenuation has creeped from 61 to 59 in the last couple of weeks... is this normal?

Fitting all the ADSL faceplate stuff tommorrow... will be interesting to see what this does for me.  Will cross my fingers and hope!

AvengerUK have you fitted an ADSL faceplate yet?

[AvengerUK]

AvengerUK have you fitted an ADSL faceplate yet?

Nope, may be also something ill do soon

My DS Margin seems to change every 5 or so mins (or more) i dont really see a change in what time of day it is, it just bob's up and down constantly

[mrapoc]

ive been having high pings and connection problems more often over the last week (i have them occasionally but usually a router reboot fixes it) and im usually constant 8000kbps connection...just checked now and its at 6,176 

[Jeff]

This can only be good news Rich, 6.6 steady is good. Rule of thumb, every 6SNR=0.8Mbit, sync being determined by DS margin in the first place so I reckon if you had a router that has been proven to hold sync at even SNR 0 (such as a few Netgears) then you would only probably then have a far worse sync with only a 0.8Mbit sync rate improvement ... given your poor throughput atm, hardly seems worth it?

[Richdog]

This can only be good news Rich, 6.6 steady is good. Rule of thumb, every 6SNR=0.8Mbit, sync being determined by DS margin in the first place so I reckon if you had a router that has been proven to hold sync at even SNR 0 (such as a few Netgears) then you would only probably then have a far worse sync with only a 0.8Mbit sync rate improvement ... given your poor throughput atm, hardly seems worth it?

Jeff you'll have to excuse me here as i've had a couple of beers and half a bottle of wine... what are you saying is hardly worth it?

*hic* 

EDIT - I just did a random check and the noise margin just dropped to 4.3... guess I was wrong! 

EDIT EDIT - Now 3.8!

[AvengerUK]

Anyone have any thoughts on the below? Its *perhaps* an alternative to the ZyXcel:


Im willing to spend alot of time & money simply to get a more stable connection

[Richdog]

Im willing to spend alot of time & money simply to get a more stable connection

Get a Draytek then.

[AvengerUK]

Perhaps not that much

[Richdog]

Perhaps not that much

DrayTek Vigor2700V VoIP ADSL2+ Router £130 http://www.transparentcommunications.com/acatalog/DrayTekVigor2700Series.html

Not that bad!

[AvengerUK]

For a student...its bad lol - £80 is my max

[Jeff]

Locked ... only because of my inability to keep up 

But folk, start a new topic if y`all still having bother with the original subject which I believe was  "pings"

Any newcomers ... plz start a new thread!