IDNet and latency

[kelevra]

Hi Guys,

Have just switched over to INet (awaiting activation) and was wondering what kind of latency you guys get?

Play alot of online games BFBC2, Counter-Strike, WoW and latency is a big issue for me.

If some of you could post tracert's to popular sites that would be great

Thanks 

[Rik]

I'm no gamer, so not the best person to help. If you post me some URLs, I'll gladly check them for you though. As a reference, a ping to www.idnet.net is 13-15ms for me.

[Rik]

Where are my manners.  Welcome to the forum.

[Ray]

 

[kelevra]

Cheers Rik and Ray

That ping looks very nice anything near that will be fantastic.

[Rik]

If your line is interleaved, which mine is not, you would have to add 10-20ms to my times.

[Simon]

[kelevra]

Is it possible to apply for the line to have interleaving turned off before activation? Or is this something i need to request afterwards?

Thanks

[Rik]

It will start on auto, which should mean off. BT's dynamic line management software (DLM) will then tweak the line for best performance. It will start by going for maximum speed, then looking at stability. It will either use interleaving (normally the first choice) and/or increased target noise margin until it finds a stable level. You can request interleaving to be turned off, but if that produces instability, it will be turned straight back on and BT will generally not switch it off manually a second time. If you are migrating, your current settings will move with you.

[kelevra]

Ah thats great then my current settings are interleaving OFF and the line is very stable.

Thanks for all the assistance guys  

[Rik]

Our pleasure, thanks.

[psp83]

Here's some pings for you.

C:\Users\Paul>tracert www.bbc.co.uk

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

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    13 ms    13 ms    13 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    14 ms    13 ms    13 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    14 ms    13 ms    14 ms  212.58.238.129
  6    14 ms    14 ms    15 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  7    14 ms    14 ms    17 ms  212.58.255.12
  8    15 ms    14 ms    14 ms  fmt-vip02.cwwtf.bbc.co.uk [212.58.246.159]

Trace complete.

C:\Users\Paul>tracert www.jolt.co.uk

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    14 ms    13 ms    14 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    14 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    14 ms    13 ms    14 ms  linx-brocade1.netrino.co.uk [195.66.225.18]
  5    15 ms    14 ms    14 ms  bs1-core.netrino.co.uk [84.234.19.5]
  6    21 ms    41 ms    15 ms  bruce.ferrago.net [84.234.17.86]

Trace complete.


C:\Users\Paul>tracert www.multiplay.co.uk

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

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    13 ms    17 ms    13 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    14 ms    13 ms    13 ms  lonap1.enta.net [193.203.5.134]
  5    14 ms    14 ms    14 ms  te5-2.gs1.core.enta.net [87.127.236.42]
  6    14 ms    14 ms    13 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  7    14 ms    14 ms    14 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  8    13 ms    15 ms    13 ms  www.multiplay.co.uk [85.236.96.68]

Trace complete.

[psp83]

And here's a random BFBC2 UK Server IP address I found on google.

C:\Users\Paul>tracert 217.163.28.105

Tracing route to 217.163.28.105 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    14 ms    13 ms    14 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    14 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    13 ms    14 ms    13 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
  5    14 ms    14 ms    13 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
  6    13 ms    13 ms    13 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.18]
  7    13 ms    13 ms    14 ms  level3.lon01.atlas.cogentco.com [130.117.14.198]
  8    15 ms    13 ms    13 ms  217.163.28.105

Trace complete.

[zappaDPJ]

 

Pinging some of the same servers...

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping www.jolt.co.uk

Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=12ms TTL=123
Reply from 84.234.17.86: bytes=32 time=12ms TTL=123
Reply from 84.234.17.86: bytes=32 time=12ms TTL=123
Reply from 84.234.17.86: bytes=32 time=12ms TTL=123

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

C:\Users\zappaDPJ>ping 217.163.28.105

Pinging 217.163.28.105 with 32 bytes of data:
Reply from 217.163.28.105: bytes=32 time=12ms TTL=121
Reply from 217.163.28.105: bytes=32 time=10ms TTL=121
Reply from 217.163.28.105: bytes=32 time=11ms TTL=121
Reply from 217.163.28.105: bytes=32 time=10ms TTL=121

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

C:\Users\zappaDPJ>

Obviously the quality of the infrastructure local to you will have some relevance but in general pings on IDNet are lower than any other ISP I've encountered.

[esh]

The lowest ping time is at 4am, the peak ping time is at 8pm, the difference between being about 8ms. Interleaving difference for me was about 10-15 ms. Most main sites I get 20-23 ms average. I can test a few games if you are interested.

[kelevra]

Oh dear

Have swapped over today and latency is worse than with my previous supplier.

Line APPEARS to still be interleaved however i was told that the configuration on the line would remain.

Has anyone had this problem on mingration to IDnet?

[Rik]

I haven't, either in my original migration or the move to WBC. Can you give me your router stats.

[kelevra]

ADSL   Type   Fast
Status   No Defect
                     Downstream                Upstream

Data rate           8128                                448

Noise margin   10.9                                23.0

Output power   19.7                                 11.9

Attenuation   31.0                                        19.0

[kelevra]

Reply from 217.163.28.105: bytes=32 time=35ms TTL=121
Reply from 217.163.28.105: bytes=32 time=33ms TTL=121
Reply from 217.163.28.105: bytes=32 time=33ms TTL=121
Reply from 217.163.28.105: bytes=32 time=42ms TTL=121

[Rik]

I've checked with support. For some reason, BT put interleaving on your line, they have already requested that it be removed and that should happen tomorrow.

[Steve]

Mine are unbelievable at present- adslmax non interleaved

64 bytes from 217.163.28.105: icmp_seq=0 ttl=121 time=11.553 ms
64 bytes from 217.163.28.105: icmp_seq=1 ttl=121 time=11.517 ms
64 bytes from 217.163.28.105: icmp_seq=2 ttl=121 time=9.419 ms
64 bytes from 217.163.28.105: icmp_seq=3 ttl=121 time=10.087 ms
64 bytes from 217.163.28.105: icmp_seq=4 ttl=121 time=9.893 ms
64 bytes from 217.163.28.105: icmp_seq=5 ttl=121 time=10.687 ms
64 bytes from 217.163.28.105: icmp_seq=6 ttl=121 time=9.872 ms
64 bytes from 217.163.28.105: icmp_seq=7 ttl=121 time=9.567 ms
64 bytes from 217.163.28.105: icmp_seq=8 ttl=121 time=9.352 ms
64 bytes from 217.163.28.105: icmp_seq=9 ttl=121 time=10.407 ms

[Rik]

ping www.idnet.net -t -n 10

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59

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

Interleaving off.

[kelevra]

Thanks Rik you are a star

[Rik]

Not I, mate, support had already spotted it and put in the modify order when I called. They're good like that.

[fozy994]

Hi guys,

I just switched today for similar purposes as Kelevra- and I am experiencing the same difficulties with latency (higher than previous ISP).

#

Stream Type
   

Actual Data Rate

Up Stream
   

448 (Kbps.)

Down Stream
   

7648 (Kbps.)

    * [Go Top]

# Operation Data / Defect Indication:
Operation Data

Operation Data
   

Upstream
   

Downstream

Noise Margin
   

6 dB
   

22 dB

Attenuation
   

25 dB
   

--- dB


TRACERT:

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

C:\Documents and Settings\Owner>ping www.bbc.co.uk

Pinging www.bbc.co.uk [212.58.244.143] with 32 bytes of data:

Reply from 212.58.244.143: bytes=32 time=32ms TTL=57
Reply from 212.58.244.143: bytes=32 time=31ms TTL=57
Reply from 212.58.244.143: bytes=32 time=30ms TTL=57
Reply from 212.58.244.143: bytes=32 time=31ms TTL=57

Ping statistics for 212.58.244.143:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 32ms, Average = 31ms

C:\Documents and Settings\Owner>


Box of chocolates for anyone who can help 


Foz