Reducing my ping times

Pho

Pho

Soldato
Joined
18 Oct 2002
Posts
9,329
Location
Derbyshire
I'm not greatly bothered, the ping is still low, but having seen people with even half the ping (with Nildram, too) I thought I may as well look into it.

I'm using a wired connection to my router (about 2 meters worth of network cable from the pc) which then connects to the master phone socket (again, about 2 meters from the router). I've also tried using a couple of different Microfilters.

I'm currently using a D-Link DSL-G604T with Nildram 8mb. I had similar pings (if not a couple of ms lower) when I was still with Pipex, using a different router (which I don't have anymore). I'm guessing this is generally due to the fact I live in a village so am probably not directly on a fast pipe. There are no problems with congestion and whatever on my exchange according to various online sites, and the ping remains the same throughout anytime of the day.

Router stats:
Code:
DSL Status
  	Connection Status 	Connected
  	Upstream Rate (Kbps) 	448
  	Downstream Rate (Kbps) 	8128
  	US Margin 	26
  	DS Margin 	10
  	Modulation 	GDMT
  	LOS Errors 	0
  	DS Line Attenuation 	6
  	US Line Attenuation 	3
  	Path Mode 	Fast Path
 
DSL Statistics
  	Near End F4 Loop Back Count 	0
  	Near End F5 Loop Back Count 	0


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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    31 ms    30 ms    30 ms  lo1-lon3-adsl21.nildram.net [195.112.5.30]
  3    29 ms    29 ms    30 ms  ge-1-1-1.cr2.gs1.bb.pipex.net [84.12.224.33]
  4    29 ms    30 ms    29 ms  lon1-9.nildram.net [84.12.224.14]
  5    30 ms    30 ms    40 ms  g3-18.cr05.tn5.bb.pipex.net [62.72.141.37]
  6    30 ms    30 ms    32 ms  pipex-te4-3-503.thdo.bbc.co.uk [62.72.139.66]
  7    30 ms    30 ms    31 ms  212.58.238.129
  8    30 ms    30 ms    30 ms  212.58.238.145
  9    30 ms    29 ms    30 ms  www7.rbsov.bbc.co.uk [212.58.227.77]

Trace complete.

Code:
Tracing route to [url]www.jolt.co.uk[/url] [82.133.85.65]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    31 ms    30 ms    31 ms  lo1-lon3-adsl21.nildram.net [195.112.5.30]
  3    30 ms    29 ms    29 ms  ge-1-1-1.cr2.gs1.bb.pipex.net [84.12.224.33]
  4    30 ms    30 ms    30 ms  lon1-9.nildram.net [84.12.224.14]
  5    31 ms    30 ms    29 ms  jolt-gw.nildram.net [195.149.20.214]
  6    30 ms    30 ms    30 ms  secure.jolt.co.uk [82.133.85.65]

Trace complete.

The first hop always seems pretty high, possibly due to BT? (most things are ;))

I get the same ping results from doing it internally within my router bypassing any computers.

Any ideas? Thanks.
 
It's unlikely there's anything you can do, not that it has anything to do with being in a village or not being on a "fast pipe".

Edit: For what it's worth:

traceroute to www.bbc.net.uk (212.58.227.78), 30 hops max, 40 byte packets
1 0.838 ms 1.066 ms 1.126 ms
2 gauthier-dsl1.hq.zen.net.uk (62.3.82.17) 30.876 ms 29.082 ms 32.501 ms
3 lotze-ge-0-0-1-136.hq.zen.net.uk (62.3.80.137) 29.827 ms 29.622 ms 28.326 ms
4 deleuze-ge-0-2-0-0.hq.zen.net.uk (62.3.80.58) 29.572 ms 29.339 ms 30.586 ms
5 erazmus-ge-0-0-3-0.wh.zen.net.uk (62.3.80.34) 31.436 ms 28.716 ms 37.943 ms
6 lorenz-so-0-1-0-0.te.zen.net.uk (62.3.80.45) 35.940 ms 57.961 ms 38.192 ms
7 82.71.254.134 (82.71.254.134) 199.467 ms 180.792 ms 36.209 ms
8 212.58.238.153 (212.58.238.153) 36.196 ms 36.900 ms 38.832 ms
9 212.58.238.161 (212.58.238.161) 38.438 ms 37.390 ms 38.830 ms
10 www8.rbsov.bbc.co.uk (212.58.227.78) 36.688 ms 35.581 ms 37.452 ms

traceroute to www.jolt.co.uk (82.133.85.65), 30 hops max, 40 byte packets
1 0.730 ms 0.686 ms 0.736 ms
2 gauthier-dsl1.hq.zen.net.uk (62.3.82.17) 44.071 ms 43.231 ms 42.066 ms
3 lotze-ge-0-0-1-136.hq.zen.net.uk (62.3.80.137) 40.307 ms 43.215 ms 44.067 ms
4 deleuze-ge-0-2-0-0.hq.zen.net.uk (62.3.80.58) 41.947 ms 48.587 ms 45.052 ms
5 suarez-so-0-0-0-0.te.zen.net.uk (62.3.80.62) 51.448 ms 48.745 ms 51.200 ms
6 te1-3.cr05.tn5.bb.pipex.net (195.66.224.29) 44.074 ms 48.454 ms 52.942 ms
7 ge-0-2-0.lon1-9.nildram.net (62.72.141.38) 51.322 ms 52.395 ms 48.568 ms
8 jolt-gw.nildram.net (195.149.20.214) 50.700 ms 49.990 ms 56.318 ms
9 secure.jolt.co.uk (82.133.85.65) 49.303 ms 52.547 ms 50.187 ms
 
Fair enough then :). As said, I'm not entirely bothered just it would be nice if their was something I was completely missing. Thanks anyway.
 
You're on Fast mode already, and your first hop ping is high, which shows it's probably caused by BT. Do you know what RAS you're connected to?

For reference:

olly-powermac:~ olly$ traceroute 82.133.85.65
traceroute to 82.133.85.65 (82.133.85.65), 64 hops max, 40 byte packets
1 firebrick-lan.office.miniserve.net (81.187.156.129) 2.310 ms 1.294 ms 1.518 ms
2 zyxel2-lan.office.miniserve.net (81.187.95.242) 2.641 ms zyxel1-lan.office.miniserve.net (81.187.95.241) 1.867 ms 1.876 ms
3 careless.aaisp.net.uk (81.187.81.72) 15.809 ms 17.352 ms 15.183 ms
4 aimless.aaisp.net.uk (217.169.20.3) 16.347 ms 21.702 ms 19.746 ms
5 186.ge1-0.er1a.lhr4.uk.above.net (213.161.69.146) 17.011 ms 15.740 ms 19.158 ms
6 so-2-2-0.cr2.lhr4.uk.above.net (208.184.231.129) 15.910 ms 16.757 ms 20.071 ms
7 pos7-0.mpr2.lhr1.uk.above.net (208.184.231.169) 16.790 ms 18.038 ms 16.633 ms
8 gxn-pi-above-1000mbps.lhr.above.net (209.249.203.138) 18.653 ms 17.890 ms 17.495 ms
9 ge-0-2-0.lon1-9.nildram.net (62.72.141.38) 16.847 ms 18.389 ms 21.608 ms
10 jolt-gw.nildram.net (195.149.20.214) 17.149 ms 15.541 ms 18.482 ms
11 secure.jolt.co.uk (82.133.85.65) 20.972 ms 20.025 ms 17.649 ms

and

olly-powermac:~ olly$ traceroute 212.58.227.77
traceroute to 212.58.227.77 (212.58.227.77), 64 hops max, 40 byte packets
1 firebrick-lan.office.miniserve.net (81.187.156.129) 1.969 ms 2.294 ms 1.202 ms
2 zyxel2-lan.office.miniserve.net (81.187.95.242) 1.845 ms zyxel1-lan.office.miniserve.net (81.187.95.241) 2.930 ms zyxel2-lan.office.miniserve.net (81.187.95.242) 1.936 ms
3 careless.aaisp.net.uk (81.187.81.72) 20.295 ms 15.527 ms 20.176 ms
4 aimless.aaisp.net.uk (217.169.20.3) 15.652 ms 17.158 ms 15.740 ms
5 xpe-gw0.prt0.thdo.bbc.co.uk (217.79.160.123) 18.869 ms 18.530 ms 15.460 ms
6 212.58.238.129 (212.58.238.129) 19.539 ms 20.291 ms 16.348 ms
7 212.58.238.145 (212.58.238.145) 18.545 ms 18.182 ms 16.500 ms
8 www7.rbsov.bbc.co.uk (212.58.227.77) 18.552 ms 19.512 ms 16.701 ms
 
Doesn't look like there's much (if anything at all) you can do with yours as you don't have interleaving on at the moment as the others have said.
 
TiZoR said:
what isp are you with

tolien said:
Code:
2 gauthier-dsl1.hq.zen.net.uk (62.3.82.17) 44.071 ms 43.231 ms 42.066 ms
3 lotze-ge-0-0-1-136.hq.[b]zen.net.uk[/b] (62.3.80.137) 40.307 ms 43.215 ms 44.067 ms
4 deleuze-ge-0-2-0-0.hq.[b]zen.net.uk[/b] (62.3.80.58) 41.947 ms 48.587 ms 45.052 ms
5 suarez-so-0-0-0-0.te.[b]zen.net.uk[/b] (62.3.80.62) 51.448 ms 48.745 ms 51.200 ms

Enough of a give away? :D
 
OllyM said:
You're on Fast mode already, and your first hop ping is high, which shows it's probably caused by BT. Do you know what RAS you're connected to?

When connecting to the BT test account and tracing to BT(which apparently works according to a website I found):

It's:
esr2.sheffield3.broadband.bt.net [217.47.73.141] - which will be around 50 miles roughly from here.
 
Check my times out, and you think your times are bad :eek: :(

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

1 3000 ms 36 ms 34 ms lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
2 34 ms 34 ms 33 ms ge0-0-0-504.pte-gw1.plus.net [84.92.4.89]
3 34 ms 34 ms * 195.50.117.169
4 34 ms 34 ms 34 ms ae-0-51.bbr1.London1.Level3.net [4.68.116.1]
5 55 ms 51 ms 49 ms ae-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.2
9]
6 53 ms 49 ms 50 ms ae-22-56.car2.Frankfurt1.Level3.net [4.68.118.17
6]
7 50 ms 49 ms 50 ms telia-level3-ge.Frankfurt1.Level3.net [4.68.111.
102]
8 50 ms 51 ms 51 ms ffm-bb2-link.telia.net [80.91.249.193]
9 61 ms 61 ms 60 ms prs-bb2-pos7-0-0.telia.net [213.248.65.117]
10 50 ms 50 ms 50 ms ldn-bb2-pos7-0-0.telia.net [213.248.65.113]
11 51 ms 50 ms 52 ms ldn-b3-pos9-0.telia.net [213.248.64.50]
12 52 ms 49 ms 51 ms pipex-110586-ldn-b3.c.telia.net [213.248.100.30]

13 52 ms 53 ms 50 ms lon1-9.nildram.net [84.12.224.14]
14 * * 53 ms jolt-gw.nildram.net [195.149.20.214]
15 51 ms 52 ms 53 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.
 
do i beat you all? ;)

traceroute to www.jolt.co.uk (82.133.85.65), 30 hops max, 38 byte packets
1 149.170.13.252 (149.170.13.252) 0.466 ms 0.333 ms 0.361 ms
2 danae.stu.mmu.ac.uk (149.170.1.254) 0.485 ms 0.331 ms 0.235 ms
3 10.4.30.254 (10.4.30.254) 0.485 ms 0.555 ms 0.357 ms
4 sage-central.mmu.ac.uk (149.170.189.254) 0.868 ms 0.711 ms 0.735 ms
5 149.170.189.186 (149.170.189.186) 1.613 ms 1.226 ms 0.860 ms
6 * * *
7 * * *
8 gw-nnw.core.netnw.net.uk (194.66.25.97) 2.399 ms 1.710 ms 1.731 ms
9 manchester-bar.ja.net (146.97.40.201) 2.360 ms 1.842 ms 1.735 ms
10 po11-0.warr-scr.ja.net (146.97.35.165) 3.236 ms 2.593 ms 2.361 ms
11 po3-0.read-scr.ja.net (146.97.33.53) 6.484 ms 5.964 ms 9.856 ms
12 po1-0.lond-scr4.ja.net (146.97.33.25) 8.226 ms 7.087 ms 7.358 ms
13 * * *
14 g3-32.cr05.tn5.bb.pipex.net (62.72.139.101) 8.091 ms 7.331 ms 7.480 ms
15 * * *
16 * * *
17 secure.jolt.co.uk (82.133.85.65) 8.611 ms 7.708 ms 7.980 ms
 
Blueyonder cable

Code:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     8 ms  10.15.0.1
  3     8 ms    18 ms     7 ms  195.188.230.193
  4    22 ms    21 ms    22 ms  195.188.230.81
  5    16 ms    16 ms    15 ms  195.188.230.26
  6    21 ms    21 ms    21 ms  194.117.136.238
  7    20 ms    22 ms    19 ms  194.117.136.154
  8    16 ms    16 ms    15 ms  194.117.136.169
  9    36 ms    20 ms    20 ms  194.117.136.166
 10    16 ms    29 ms    18 ms  tele2-gw4.telewest.net [194.117.136.197]
 11    21 ms    39 ms    21 ms  pipex-telewest-pvtpeer.telewest.net [194.117.147.38]
 12    16 ms    18 ms    16 ms  ge-0-2-0.lon1-9.nildram.net [62.72.141.38]
 13    26 ms    23 ms    22 ms  jolt-gw.nildram.net [195.149.20.214]
 14    16 ms    22 ms    16 ms  secure.jolt.co.uk [82.133.85.65]
 
Clarkey said:
do i beat you all? ;)

Nope.

paul@thor:~:$ ping -c 10 jolt.co.uk
PING jolt.co.uk (82.133.85.65) 56(84) bytes of data.
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=1 ttl=55 time=3.85 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=2 ttl=55 time=3.79 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=3 ttl=55 time=4.43 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=4 ttl=55 time=3.65 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=5 ttl=55 time=4.00 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=6 ttl=55 time=6.88 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=7 ttl=55 time=3.64 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=8 ttl=55 time=3.93 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=9 ttl=55 time=3.74 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=10 ttl=55 time=4.17 ms

--- jolt.co.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9095ms
rtt min/avg/max/mdev = 3.646/4.214/6.885/0.921 ms
 
im on zen maxdsl and had interleaving taken off by my request, im in South Wales

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 20 ms 20 ms gadamer-dsl.zen.net.uk [62.3.83.3]
3 21 ms 20 ms 20 ms erazmus-ge-0-0-1-1.wh.zen.net.uk [62.3.80.193]
4 26 ms 26 ms 26 ms lorenz-so-0-1-0-0.te.zen.net.uk [62.3.80.45]
5 26 ms 26 ms 26 ms te1-3.cr05.hx2.bb.pipex.net [195.66.226.29]
6 27 ms 27 ms 27 ms v3952.cr05.tn5.bb.pipex.net [62.72.137.9]
7 26 ms 26 ms 27 ms ge-0-2-0.lon1-9.nildram.net [62.72.141.38]
8 28 ms 28 ms 27 ms jolt-gw.nildram.net [195.149.20.214]
9 27 ms 26 ms 26 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.
 
Back
Top Bottom