dramatic change in downstream margin is it good or bad

amcclean · ‎30-07-2007

I just rebooted my router to get the following stats. Re-checking show it to vary between 1 and 2db mownstream attention however remains at 43.
DSL Status: Up
DSL Modulation Mode: GDMT
DSL Path Mode: FAST
Downstream Rate: 4480 Kbps
Upstream Rate: 448 Kbps
Downstream Margin: 2 db
Upstream Margin: 24 db
Downstream Line Attenuation: 43
Upstream Line Attenuation: 24
Downstream Transmit Power: 0
Upstream Transmit Power: 0

Cheers,
P

amcclean · ‎30-07-2007

ha ha look at this esp the ping

I had re-booted leaving router off for 1hr before my dramatic drop guess i may need to do that again

VileReynard · ‎01-09-2007

Your downstream attenuation should be almost constant - it is the line loss + anything bad at your end such as using a long phone extension.
The plusnet speedtest seems to be currently rubbish though.
Try ping www.bbc.co.uk

"In The Beginning Was The Word, And The Word Was Aardvark."

amcclean · ‎30-07-2007

no ext, bell wire etc removed years ago. line now back to normal.

amcclean · ‎30-07-2007

tonights test from two different servers the pings are awful currently on pro low ping package
never crossed my mind to try another server
1st test London

2nd test Dublin

Also here are some pings and tracert s from tonight.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=52ms TTL=122
Reply from 212.58.253.67: bytes=32 time=28ms TTL=122
Reply from 212.58.253.67: bytes=32 time=29ms TTL=122
Reply from 212.58.253.67: bytes=32 time=27ms TTL=122
Ping statistics for 212.58.253.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 52ms, Average = 34ms
C:\Users>ping www.plus.net
Pinging portal.plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=41ms TTL=250
Reply from 212.159.9.2: bytes=32 time=41ms TTL=250
Reply from 212.159.9.2: bytes=32 time=43ms TTL=250
Reply from 212.159.9.2: bytes=32 time=41ms TTL=250
Ping statistics for 212.159.9.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 41ms

C:\Users>ping www.google.co.uk
Pinging www.l.google.com [216.239.59.147] with 32 bytes of data:
Reply from 216.239.59.147: bytes=32 time=41ms TTL=246
Reply from 216.239.59.147: bytes=32 time=50ms TTL=246
Reply from 216.239.59.147: bytes=32 time=42ms TTL=246
Reply from 216.239.59.147: bytes=32 time=41ms TTL=246
Ping statistics for 216.239.59.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 50ms, Average = 43ms

supposed to be on a pro package that give low pings is ttl level in the later pings goog or bad and if high is bad where does the slowness occur?
R

Mark · ‎04-04-2007

Hi podman.
Major difference between your speedtester pings and those to the beeb.
Could you post up a tracert to both sites please?

amcclean · ‎30-07-2007

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 27 ms 25 ms lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
3 31 ms 44 ms 34 ms vl303.thn-gw2.plus.net [84.92.3.178]
4 27 ms 41 ms 29 ms rt0.thdo.bbc.co.uk [212.58.239.25]
5 28 ms 26 ms 35 ms 212.58.238.149
6 30 ms 32 ms 26 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
7 29 ms 27 ms 29 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.
C:\Users>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 39 ms 38 ms 33 ms lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
3 33 ms 40 ms 35 ms vl303.thn-gw1.plus.net [84.92.3.177]
4 29 ms 36 ms 35 ms ae0-102.ptn-gw01.plus.net [212.159.1.53]
5 32 ms 37 ms 29 ms gi0-1-31.ptc-gw1.plus.net [195.166.129.3]
6 43 ms 36 ms 38 ms pos1-0.pih-cr1.plus.net [195.166.129.250]
7 47 ms 38 ms 45 ms vlan7.pih-gw3.plus.net [212.159.0.26]
8 93 ms 38 ms 33 ms if25.pih-lb04.plus.net [212.159.0.18]
9 44 ms 47 ms 34 ms portal.plus.net [212.159.8.2]
Trace complete.
C:\Users>tracert www.google.co.uk
Tracing route to www.l.google.com [216.239.59.103]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.1.1
2 46 ms 33 ms 29 ms lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
3 46 ms 26 ms 33 ms vl303.thn-gw2.plus.net [84.92.3.178]
4 27 ms 25 ms 25 ms vl23.pte-gw2.plus.net [212.159.4.28]
5 29 ms 25 ms 26 ms 195.66.224.125
6 42 ms 32 ms 41 ms 209.85.252.40
7 52 ms 74 ms 40 ms 209.85.250.216
8 42 ms 40 ms 39 ms 64.233.174.185
9 47 ms 68 ms 61 ms 216.239.49.114
10 43 ms 42 ms 46 ms 216.239.59.103
Trace complete.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users>tracert www.speedtest.net
Tracing route to www.speedtest.net [69.17.117.207]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 27 ms 25 ms 27 ms lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
3 27 ms 26 ms 39 ms vl303.thn-gw2.plus.net [84.92.3.178]
4 28 ms 27 ms 31 ms ldn-b4-link.telia.net [213.248.84.197]
5 27 ms 26 ms 27 ms teleglobe-114869-ldn-b4.telia.net [213.248.74.2]
6 29 ms 28 ms 27 ms if-3-2.mcore3.LDN-London.teleglobe.net [195.219.
195.13]
7 25 ms 25 ms 27 ms if-5-0-0.mcore3.L78-London.teleglobe.net [195.21
9.195.10]
8 102 ms 98 ms 97 ms if-7-0.mcore4.NJY-Newark.teleglobe.net [195.219.
144.10]
9 103 ms 98 ms 107 ms if-6-0.mcore4.NQT-NewYork.teleglobe.net [216.6.6
3.42]
10 184 ms 181 ms 185 ms if-4-0.mcore4.PDI-PaloAlto.teleglobe.net [216.6.
86.13]
11 184 ms 178 ms 177 ms if-3-0.mcore3.PDI-PaloAlto.teleglobe.net [216.6.
29.65]
12 210 ms 208 ms 207 ms if-6-0.core2.SEP-Seattle.teleglobe.net [66.110.6
4.5]
13 194 ms 198 ms 186 ms ix-5-2.core2.SEP-Seattle.teleglobe.net [66.110.6
4.10]
14 194 ms 188 ms 195 ms 151.ge-1-3-0.sr1.sea5.speakeasy.net [69.17.82.50
]
15 196 ms 196 ms 196 ms www.ookla.com [69.17.117.207]
Trace complete.
C:\Users>tracert www.speedtest.net
Tracing route to www.speedtest.net [69.17.117.207]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 26 ms 31 ms 28 ms lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
3 24 ms 25 ms 35 ms vl303.thn-gw2.plus.net [84.92.3.178]
4 26 ms 34 ms 24 ms ldn-b4-link.telia.net [213.248.84.197]
5 30 ms 33 ms 27 ms teleglobe-114869-ldn-b4.telia.net [213.248.74.2]
6 33 ms 27 ms 26 ms if-3-2.mcore3.LDN-London.teleglobe.net [195.219.
195.13]
7 26 ms 29 ms 28 ms if-5-0-0.mcore3.L78-London.teleglobe.net [195.21
9.195.10]
8 186 ms 105 ms 155 ms if-7-0.mcore4.NJY-Newark.teleglobe.net [195.219.
144.10]
9 105 ms 105 ms 101 ms if-6-0.mcore4.NQT-NewYork.teleglobe.net [216.6.6
3.42]
10 208 ms 178 ms 182 ms if-4-0.mcore4.PDI-PaloAlto.teleglobe.net [216.6.
86.13]
11 282 ms 182 ms 181 ms if-3-0.mcore3.PDI-PaloAlto.teleglobe.net [216.6.
29.65]
12 402 ms 206 ms 213 ms if-6-0.core2.SEP-Seattle.teleglobe.net [66.110.6
4.5]
13 188 ms 189 ms 195 ms ix-5-2.core2.SEP-Seattle.teleglobe.net [66.110.6
4.10]
14 203 ms 199 ms 189 ms 152.ge-1-3-0.sr2.sea5.speakeasy.net [69.17.82.54
]
15 209 ms 199 ms 205 ms www.ookla.com [69.17.117.207]
Trace complete.
looks like the us may be the cause of the problem

James · ‎04-04-2007

Hiya,
I'd personally ignore the ping times that speedtester.net is giving you.
The traffic is routing to the States, otherwise your ping response seem to be pretty normal.

amcclean · ‎30-07-2007

My current starts are below. Should I be looking for an increase in sync. I used to have this downstream margin a few years ago and sync'd at 8128.
DSL Status: Up
DSL Modulation Mode: GDMT
DSL Path Mode: FAST
Downstream Rate: 4512 Kbps
Upstream Rate: 448 Kbps
Downstream Margin: 8 db
Upstream Margin: 24 db
Downstream Line Attenuation: 43
Upstream Line Attenuation: 24
Downstream Transmit Power: 0

at least pings from here are down.
Upstream Transmit Power: 0