Upstream attenuation halved?

[gymno]

Presumably i need to do a trace when the pings are silly.
They've been ok whenever i've checked, but here goes anyway.
Maybe there's something odd in there. I don't know what i'm looking for TBH.

1st link
traceroute to 176.248.xxx.xx (176.248.xxx.xx), 25 hops max, 40 byte packets
1 static-ip-188-138-112-3.inaddr.ip-pool.com (188.138.112.3) 1.833 ms
2 217.118.16.162 (217.118.16.162) 0.262 ms
3 te2-7.ccr01.sxb03.atlas.cogentco.com (149.11.26.13) 0.423 ms
4 te4-7.ccr01.sxb01.atlas.cogentco.com (154.54.62.197) 107.429 ms
5 te0-2-0-6.mpd21.fra03.atlas.cogentco.com (154.54.62.217) 3.920 ms
6 tiscali.fra03.atlas.cogentco.com (130.117.14.86) 3.590 ms
7 xe-7-0-0.lon10.ip4.tinet.net (89.149.187.101) 18.125 ms
8 easynet-gw.ip4.tinet.net (77.67.74.94) 23.305 ms
9 *
10 *
11 b0f8ba3a.bb.sky.com (176.248.xxx.xx) 43.450 ms
12 b0f8ba3a.bb.sky.com (176.248.xxx.xx) 43.711 ms

- - - Updated - - -

2nd link
Hop (ms) (ms) (ms) **** IP Address Host name
1* **0* **0* **0* **** 8.9.232.73 *xe-5-3-0.edge3.dallas1.level3.net *
2* **0* **0* **0* **** 4.69.145.62 *vlan60.csw1.dallas1.level3.net *
3* **0* **0* **0* **** 4.69.151.130 *ae-62-62.ebr2.dallas1.level3.net *
4* **34* **34* **34* **** 4.69.137.122 *ae-3-3.ebr2.newyork1.level3.net *
5* **46* **34* **38* **** 4.69.148.38 *ae-72-72.csw2.newyork1.level3.net *
6* **34* **34* **34* **** 4.69.134.69 *ae-71-71.ebr1.newyork1.level3.net *
7* **103* **103* **103* **** 4.69.137.69 *ae-42-42.ebr2.london1.level3.net *
8* **103* **111* **103* **** 4.69.153.130 *ae-56-221.csw2.london1.level3.net *
9* **103* **103* **Timed out* **** 4.69.139.106 *ae-2-52.edge4.london1.level3.net *
10* **105* **107* **107* **** 195.50.122.114 * - *
11* **Timed out* **Timed out* **Timed out* **** * - *
12* **Timed out* **Timed out* **Timed out* **** * - *
13* **128* **126* **127* **** 176.248.xxx.xx *b0f8ba3a.bb.sky.com *
Trace complete

[Shonk]

looks messed up on the second one

should look like below


traceroute to 90.218.xxx.xxx (90.218.xxx.xxx), 25 hops max, 40 byte packets
1 static-ip-188-138-112-3.inaddr.ip-pool.com (188.138.112.3) 1.788 ms
2 217.118.16.161 (217.118.16.161) 0.283 ms
3 217.118.16.30 (217.118.16.30) 0.253 ms
4 te1-8.ccr01.sxb03.atlas.cogentco.com (149.11.26.9) 0.520 ms
5 te3-4.ccr01.sxb01.atlas.cogentco.com (154.54.62.205) 0.526 ms
6 te0-2-0-6.mpd21.fra03.atlas.cogentco.com (154.54.62.217) 3.907 ms
7 xe-4-3-0.fra23.ip4.tinet.net (77.67.74.41) 3.615 ms
8 xe-1-3-0.lon80.ip4.tinet.net (89.149.182.94) 16.028 ms
9 easynet-gw.ip4.tinet.net (77.67.65.174) 24.288 ms
10 *
11 cr1.xxxxx.uk.easynet.net (87.87.xxx.xxx) 24.790 ms
12 xxx.bb.sky.com (90.218.xxx.xxx) 26.973 ms



Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
2 11 0 0 4.69.145.62 vlan60.csw1.dallas1.level3.net
3 0 0 0 4.69.151.130 ae-62-62.ebr2.dallas1.level3.net
4 34 34 34 4.69.137.122 ae-3-3.ebr2.newyork1.level3.net
5 34 40 34 4.69.148.46 ae-92-92.csw4.newyork1.level3.net
6 34 34 34 4.69.134.77 ae-91-91.ebr1.newyork1.level3.net
7 103 103 103 4.69.137.69 ae-42-42.ebr2.london1.level3.net
8 103 103 103 4.69.153.130 ae-56-221.csw2.london1.level3.net
9 Timed out Timed out Timed out -
10 106 107 107 195.50.122.114 -
11 Timed out Timed out Timed out -
12 110 111 111 87.87.xxx.xxx cr1.xxxxx.uk.easynet.net
13 113 113 113 90.218.xxx.xxx xxx.bb.sky.com

- - - Updated - - -

actually ignore that

the *** are your edits
they look fine atm

[gymno]

Hi shonk.

I've done the 2nd one several times in the past, whenever my ip has changed.
It seems to come out quite different with each ip.
I think when i was on a 90. it would complete on 118ms.
When on a 2. the last 2 entries would be time outs.

Don't qoute me on that though!

Just read your edit...
It's actually my browser.
Whenever i copy/paste something with spaces, * appear everywhere

[Shonk]

the ip address you get wont make any difference to the routing

12 110 111 111 87.87.xxx.xxx cr1.xxxxx.uk.easynet.net

that is the exchange in my case

so its 111ms to the easynet core router in my exchange
then 2.5ms more to me

here's yours

12* **Timed out* **Timed out* **Timed out* **** * - *

it doesnt seem to reply to pings for some reason
take off 20ms for your delays and imp
and its 107ms to the exchange which is fine

[gymno]

OK, so my pings seem to have been back to normal since 10p.m. last night.

I just did a reboot (off at mains for 2 mins) to see if my upstream attenuation would return to the usual 14.3db...

ADSL Link Downstream Upstream
Connection Speed 19999*kbps 1172*kbps
Line Attenuation 23.0*dB 11.7*dB
Noise Margin 7.1*dB 9.7*dB

...not quite.

I doubt that's got anything to do with this ping issue anyway.
There's a few other people getting the same random upstream attenuations, but without any apparent issues.

I'm going to hold off calling sky until my pings go silly again.
Hopefully, if i can get through while it's happening, they'll be able to see some hefty errors & know for sure that there's something wrong.

Thanks for your help guys

[snadge]

it sounds to me like its capacity issue - like mine was and i had attenuation all over the shop

@ NilSatisOptimum - which router you using?

maybe if you could get past a regular "first tier" rep and get through to a 'Broadband Technical Advisor' he will be able to communicate with the Telent Engineer who manages your exchange and see if can find out any info - I mean they said mine was over capacity but on their website it said it was fine, seems like the post code checker isnt always updated, or at least straight away - i checked mine for weeks afterwards and the post code checker never once said it was over capacity, but I was told it was and it would be put right, i assume it has been - no more attenuation fluctuations - before my problems I was having some ping issues like yours during peak hours only, I had complained to sky and they said it was fine, months later is when they said it was over capacity - so the shoe fits! , mine was defo over capacity and symptoms were odd pings and fluctauting upstream attenuation

[gymno]

Just rebooted & attenuation is back to normal.

ADSL Link Downstream Upstream
Connection Speed 19998*kbps 1172*kbps
Line Attenuation 23.0*dB 14.3*dB
Noise Margin 7.0*dB 9.2*dB

I don't know if it's stable or random as i don't want to set dlm off with lots of reboots.

Pings have also been fine, atleast whenever i've checked (which i'll be doing a lot of at peak times now).

[snadge]

yeah too many reboots will force DLM to kick in, it will raise Interleaving depth and Impulse Noise Protection values - may even raise noise margin

[gymno]

No wonder i can't get into a game tonight

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=37.9 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=53.5 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=38.3 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=34.6 ms

--- 212.58.241.131 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 34.6/41.0/53.5 ms

Ping to bbc - normally 24ms

[gymno]

PING 212.58.241.131 (212.58.241.131): 56 data bytes
56 bytes from 212.58.241.131: icmp_seq=0 ttl=247 time=35.7 ms
56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=27.3 ms
56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=55.4 ms
56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=45.1 ms

--- 212.58.241.131 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 27.3/40.8/55.4 ms

This line behaviour effectively destroys my hobby & i'm paying sky for the privilege .

Can anyone please advise me on what i should do or say next as i'm now at the end of my tether