Your forum username:
Do you already have an account?
Forgot your password?
  • Log in or Sign up


    Welcome to Sky User - The Unofficial Support Forum for everything Sky! - Proudly helping over 65k members.


    Advertisement

    Results 1 to 10 of 10

    ping spikes & upstream attenuation halved

    This is a discussion on ping spikes & upstream attenuation halved within the Sky Broadband help forums, part of the Sky Broadband help and support category; Hi folks. I was just going to ask how i might go about stabilising my pings, but last night my ...

    1. #1
      gymno's Avatar
      gymno Guest
      Exchange:
      Broadband ISP:
      Router:
      Sky TV:

      ping spikes & upstream attenuation halved

      Hi folks.
      I was just going to ask how i might go about stabilising my pings, but last night my stats went a bit strange too...

      Since a 'lift & shift' was done on my line 6 days ago, i've had these stats:

      ADSL Link Downstream Upstream
      Connection Speed 19922*kbps 1161*kbps
      Line Attenuation 23.0*dB 14.6*dB
      Noise Margin 7.1*dB 9.3*dB

      With a typical ping result, using the tool on the routers diagnostic page of:

      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=25.0 ms
      56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=24.9 ms
      56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=24.7 ms
      56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=25.5 ms

      Not bad, but approx 1 in 10 tests would result in something like this:

      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=24.0 ms
      56 bytes from 212.58.241.131: icmp_seq=1 ttl=247 time=24.4 ms
      56 bytes from 212.58.241.131: icmp_seq=2 ttl=247 time=38.7 ms <<<
      56 bytes from 212.58.241.131: icmp_seq=3 ttl=247 time=24.5 ms

      Then at 9pm last night, my downstream noise margin went low:

      ADSL Link Downstream Upstream
      Connection Speed 19922*kbps 1161*kbps
      Line Attenuation 23.0*dB 14.6*dB
      Noise Margin 5.6*dB 9.3*dB

      Having just had a noise fault on my line fixed, i thought 'here we go again' however the noise margins weren't fluctuating & the landline was/is fine.
      As an experiment, i rebooted the router with those stats to trim off some speed, just to see if it helped with my pings & to my surprise my upstream attenuation went down:

      ADSL Link Downstream Upstream
      Connection Speed 19077*kbps 1164*kbps
      Line Attenuation 23.0*dB 10.0*dB
      Noise Margin 7.1*dB 9.6*dB

      I did another reboot with the same stats this morning & it's gone down again;

      ADSL Link Downstream Upstream
      Connection Speed 19126*kbps 1168*kbps
      Line Attenuation 23.0*dB 7.6*dB
      Noise Margin 7.1*dB 9.0*dB

      I still have the ping spikes into the high 30's but it's more like 1 in 20 tests now though.

      Does anybody know what's going on here?
      Prior to the lift & shift, i would easily sync in at 19999 / 1175 & pings would be 23- 25ms with no spikes.


    2. Advertisement
    3. #2
      Shonk's Avatar
      Shonk is online now Sky User Member
      Exchange:
      Broadband ISP: Sky Fibre Unlimited Pro
      Router: Asus RT-AC88U
      Sky TV: Sky+ HD
      Join Date
      Mar 2010
      Posts
      1,460
      Thanks
      7
      Thanked 118 Times in 113 Posts

      Re: ping spikes & upstream attenuation halved

      ICMP is a low priority
      and most routers reply in theyr own good time
      it generally doesnt indicate a fault

      if you are getting lots its worth checking your crc errors though
      Attached Files Attached Files

    4. #3
      gymno's Avatar
      gymno Guest
      Exchange:
      Broadband ISP:
      Router:
      Sky TV:

      Re: ping spikes & upstream attenuation halved

      Thanks for your reply shonk.
      I know this is your field & i'm glad you've taken a look

      Unfortunately i'm a bit hampered here as i only own a ps3.
      I can't therefore check for crc errors, or do proper cmd prompts or traceroutes.
      My basic browser also can't deal with your link. I'm guessing it's a pdf?

      Anyway, my bb is all about gaming for me & my research has led my to believe that a stable ping is perhaps more desirable than a low, fluctuating one?
      If this is correct, i can't help thinking these spikes could be holding me back, especially in fps games like black ops & killzone3 which i'm currently into.

      The fact i've lost 1mb downstream speed & have a stupenously low upstream attenuation now is really just a side issue.
      It's a bit strange though & maybe connected?

      Any advice would be greatly appreciated

    5. #4
      Shonk's Avatar
      Shonk is online now Sky User Member
      Exchange:
      Broadband ISP: Sky Fibre Unlimited Pro
      Router: Asus RT-AC88U
      Sky TV: Sky+ HD
      Join Date
      Mar 2010
      Posts
      1,460
      Thanks
      7
      Thanked 118 Times in 113 Posts

      Re: ping spikes & upstream attenuation halved

      I would take a lower downstream sync all day long to ensure a stable low hard crc error rate

      and i do i drop mine from 22meg to 19meg to make sure its as good as i can get it

      but saying that my attenuation never ever moves in the slightest
      this may well be a sign of a dry joint or something on the line
      as i could drop my downstream sync to 15meg and my upstream attenuation would still be 6db

    6. #5
      gymno's Avatar
      gymno Guest
      Exchange:
      Broadband ISP:
      Router:
      Sky TV:

      Re: ping spikes & upstream attenuation halved

      Google.com seems better:

      PING 173.194.34.133 (173.194.34.133): 56 data bytes
      56 bytes from 173.194.34.133: icmp_seq=0 ttl=58 time=24.2 ms
      56 bytes from 173.194.34.133: icmp_seq=1 ttl=58 time=24.8 ms
      56 bytes from 173.194.34.133: icmp_seq=2 ttl=58 time=24.3 ms
      56 bytes from 173.194.34.133: icmp_seq=2 ttl=58 time=24.3 ms

      Took well over 20 tests before this happened:

      PING 173.194.34.133 (173.194.34.133): 56 data bytes
      56 bytes from 173.194.34.133: icmp_seq=0 ttl=58 time=24.0 ms
      56 bytes from 173.194.34.133: icmp_seq=1 ttl=58 time=24.4 ms
      56 bytes from 173.194.34.133: icmp_seq=2 ttl=58 time=28.3 ms
      56 bytes from 173.194.34.133: icmp_seq=3 ttl=58 time=23.9 ms

      bbc.co.uk is quite bad at the moment though.
      I'm getting a high 30ms spike every 7th or 8th test.

      I'm using [backpage], ping, [backpage], ping, for a test every 4 seconds or so lol.

      Think i'll sit tight until monday night & if things haven't changed, give sky a call.
      They should atleast be able to tell me what my errors are like.

      EDIT: Another reboot, another attenuation figure:

      ADSL Link Downstream Upstream
      Connection Speed 19099*kbps 1164*kbps
      Line Attenuation 23.0*dB 8.8*dB
      Noise Margin 7.1*dB 9.3*dB
      Last edited by gymno; 21-07-12 at 05:03 PM. Reason: extra info

    7. #6
      Shonk's Avatar
      Shonk is online now Sky User Member
      Exchange:
      Broadband ISP: Sky Fibre Unlimited Pro
      Router: Asus RT-AC88U
      Sky TV: Sky+ HD
      Join Date
      Mar 2010
      Posts
      1,460
      Thanks
      7
      Thanked 118 Times in 113 Posts

      Re: ping spikes & upstream attenuation halved

      Here was the attachment btw
      so you can see it

      i wouldnt worry about it that much if its not to bad

      virgin users at peak time will be something like below

      25
      27
      31
      25
      55
      700
      25
      95
      25
      205
      45
      700
      25
      900
      25
      25
      25
      900
      45
      25

      etc..
      and they are the ones pulling host

      root@Nas3:~# ping 212.58.241.131
      PING 212.58.241.131 (212.58.241.131): 56 data bytes
      64 bytes from 212.58.241.131: seq=0 ttl=246 time=11.765 ms
      64 bytes from 212.58.241.131: seq=1 ttl=246 time=11.568 ms
      64 bytes from 212.58.241.131: seq=2 ttl=246 time=11.914 ms
      64 bytes from 212.58.241.131: seq=3 ttl=246 time=11.324 ms
      64 bytes from 212.58.241.131: seq=4 ttl=246 time=11.700 ms
      64 bytes from 212.58.241.131: seq=5 ttl=246 time=11.572 ms
      64 bytes from 212.58.241.131: seq=6 ttl=246 time=11.448 ms
      64 bytes from 212.58.241.131: seq=7 ttl=246 time=11.349 ms
      64 bytes from 212.58.241.131: seq=8 ttl=246 time=11.479 ms
      64 bytes from 212.58.241.131: seq=9 ttl=246 time=11.592 ms
      64 bytes from 212.58.241.131: seq=10 ttl=246 time=11.941 ms
      64 bytes from 212.58.241.131: seq=11 ttl=246 time=11.600 ms
      64 bytes from 212.58.241.131: seq=12 ttl=246 time=11.472 ms
      64 bytes from 212.58.241.131: seq=13 ttl=246 time=11.593 ms
      64 bytes from 212.58.241.131: seq=14 ttl=246 time=11.982 ms
      64 bytes from 212.58.241.131: seq=15 ttl=246 time=11.376 ms
      64 bytes from 212.58.241.131: seq=16 ttl=246 time=11.729 ms
      64 bytes from 212.58.241.131: seq=17 ttl=246 time=11.654 ms
      64 bytes from 212.58.241.131: seq=18 ttl=246 time=11.272 ms
      64 bytes from 212.58.241.131: seq=19 ttl=246 time=11.876 ms
      64 bytes from 212.58.241.131: seq=20 ttl=246 time=11.509 ms
      64 bytes from 212.58.241.131: seq=21 ttl=246 time=11.636 ms
      64 bytes from 212.58.241.131: seq=22 ttl=246 time=11.266 ms
      64 bytes from 212.58.241.131: seq=23 ttl=246 time=11.668 ms
      64 bytes from 212.58.241.131: seq=24 ttl=246 time=11.544 ms
      64 bytes from 212.58.241.131: seq=25 ttl=246 time=11.914 ms
      64 bytes from 212.58.241.131: seq=26 ttl=246 time=11.554 ms
      64 bytes from 212.58.241.131: seq=27 ttl=246 time=11.421 ms
      64 bytes from 212.58.241.131: seq=28 ttl=246 time=11.997 ms
      64 bytes from 212.58.241.131: seq=29 ttl=246 time=11.448 ms
      64 bytes from 212.58.241.131: seq=30 ttl=246 time=11.311 ms
      64 bytes from 212.58.241.131: seq=31 ttl=246 time=11.958 ms
      64 bytes from 212.58.241.131: seq=32 ttl=246 time=11.551 ms
      64 bytes from 212.58.241.131: seq=33 ttl=246 time=11.450 ms
      64 bytes from 212.58.241.131: seq=34 ttl=246 time=11.344 ms
      64 bytes from 212.58.241.131: seq=35 ttl=246 time=11.697 ms
      64 bytes from 212.58.241.131: seq=36 ttl=246 time=11.853 ms
      64 bytes from 212.58.241.131: seq=37 ttl=246 time=11.482 ms
      64 bytes from 212.58.241.131: seq=38 ttl=246 time=11.588 ms
      64 bytes from 212.58.241.131: seq=39 ttl=246 time=11.733 ms
      64 bytes from 212.58.241.131: seq=40 ttl=246 time=11.627 ms
      64 bytes from 212.58.241.131: seq=41 ttl=246 time=11.236 ms
      64 bytes from 212.58.241.131: seq=42 ttl=246 time=11.616 ms
      64 bytes from 212.58.241.131: seq=43 ttl=246 time=11.476 ms
      64 bytes from 212.58.241.131: seq=44 ttl=246 time=11.374 ms
      64 bytes from 212.58.241.131: seq=45 ttl=246 time=11.764 ms
      64 bytes from 212.58.241.131: seq=46 ttl=246 time=11.600 ms
      64 bytes from 212.58.241.131: seq=47 ttl=246 time=12.012 ms
      64 bytes from 212.58.241.131: seq=48 ttl=246 time=11.649 ms
      64 bytes from 212.58.241.131: seq=49 ttl=246 time=11.538 ms
      64 bytes from 212.58.241.131: seq=50 ttl=246 time=11.668 ms
      64 bytes from 212.58.241.131: seq=51 ttl=246 time=11.522 ms
      64 bytes from 212.58.241.131: seq=52 ttl=246 time=11.417 ms
      64 bytes from 212.58.241.131: seq=53 ttl=246 time=11.546 ms
      64 bytes from 212.58.241.131: seq=54 ttl=246 time=11.634 ms
      64 bytes from 212.58.241.131: seq=55 ttl=246 time=11.558 ms
      64 bytes from 212.58.241.131: seq=56 ttl=246 time=11.685 ms
      64 bytes from 212.58.241.131: seq=57 ttl=246 time=11.578 ms
      64 bytes from 212.58.241.131: seq=58 ttl=246 time=11.687 ms
      64 bytes from 212.58.241.131: seq=59 ttl=246 time=11.586 ms
      64 bytes from 212.58.241.131: seq=60 ttl=246 time=11.898 ms
      64 bytes from 212.58.241.131: seq=61 ttl=246 time=11.590 ms
      64 bytes from 212.58.241.131: seq=62 ttl=246 time=11.471 ms
      64 bytes from 212.58.241.131: seq=63 ttl=246 time=20.039 ms
      64 bytes from 212.58.241.131: seq=64 ttl=246 time=11.713 ms
      64 bytes from 212.58.241.131: seq=65 ttl=246 time=11.835 ms
      64 bytes from 212.58.241.131: seq=66 ttl=246 time=11.714 ms
      64 bytes from 212.58.241.131: seq=67 ttl=246 time=11.373 ms
      64 bytes from 212.58.241.131: seq=68 ttl=246 time=11.474 ms
      64 bytes from 212.58.241.131: seq=69 ttl=246 time=11.592 ms
      ^C
      --- 212.58.241.131 ping statistics ---
      70 packets transmitted, 70 packets received, 0% packet loss
      round-trip min/avg/max = 11.236/11.722/20.039 ms

    8. #7
      Shonk's Avatar
      Shonk is online now Sky User Member
      Exchange:
      Broadband ISP: Sky Fibre Unlimited Pro
      Router: Asus RT-AC88U
      Sky TV: Sky+ HD
      Join Date
      Mar 2010
      Posts
      1,460
      Thanks
      7
      Thanked 118 Times in 113 Posts

      Re: ping spikes & upstream attenuation halved

      Here's me pinging my friends 120mbit virgin media ip
      he's downloading nothing
      and it will get worse until around 2am

      PING 217.137.157.135 (217.137.157.135): 56 data bytes
      64 bytes from 217.137.157.135: seq=0 ttl=55 time=29.587 ms
      64 bytes from 217.137.157.135: seq=1 ttl=55 time=30.425 ms
      64 bytes from 217.137.157.135: seq=2 ttl=55 time=28.389 ms
      64 bytes from 217.137.157.135: seq=3 ttl=55 time=96.312 ms
      64 bytes from 217.137.157.135: seq=4 ttl=55 time=28.635 ms
      64 bytes from 217.137.157.135: seq=5 ttl=55 time=30.275 ms
      64 bytes from 217.137.157.135: seq=6 ttl=55 time=32.345 ms
      64 bytes from 217.137.157.135: seq=7 ttl=55 time=26.292 ms
      64 bytes from 217.137.157.135: seq=8 ttl=55 time=28.419 ms
      64 bytes from 217.137.157.135: seq=9 ttl=55 time=30.257 ms
      64 bytes from 217.137.157.135: seq=10 ttl=55 time=128.432 ms
      64 bytes from 217.137.157.135: seq=11 ttl=55 time=30.306 ms
      64 bytes from 217.137.157.135: seq=12 ttl=55 time=28.182 ms
      64 bytes from 217.137.157.135: seq=13 ttl=55 time=26.082 ms
      64 bytes from 217.137.157.135: seq=14 ttl=55 time=28.197 ms
      64 bytes from 217.137.157.135: seq=15 ttl=55 time=30.059 ms
      64 bytes from 217.137.157.135: seq=16 ttl=55 time=28.204 ms
      64 bytes from 217.137.157.135: seq=17 ttl=55 time=30.171 ms
      64 bytes from 217.137.157.135: seq=18 ttl=55 time=27.968 ms
      64 bytes from 217.137.157.135: seq=19 ttl=55 time=30.168 ms
      64 bytes from 217.137.157.135: seq=20 ttl=55 time=297.706 ms
      64 bytes from 217.137.157.135: seq=21 ttl=55 time=30.087 ms
      64 bytes from 217.137.157.135: seq=22 ttl=55 time=27.965 ms
      64 bytes from 217.137.157.135: seq=23 ttl=55 time=26.121 ms
      64 bytes from 217.137.157.135: seq=24 ttl=55 time=27.999 ms
      64 bytes from 217.137.157.135: seq=25 ttl=55 time=29.816 ms
      64 bytes from 217.137.157.135: seq=26 ttl=55 time=27.778 ms
      64 bytes from 217.137.157.135: seq=27 ttl=55 time=29.870 ms
      64 bytes from 217.137.157.135: seq=28 ttl=55 time=258.001 ms
      64 bytes from 217.137.157.135: seq=29 ttl=55 time=29.859 ms
      64 bytes from 217.137.157.135: seq=30 ttl=55 time=27.783 ms
      64 bytes from 217.137.157.135: seq=31 ttl=55 time=29.841 ms
      64 bytes from 217.137.157.135: seq=32 ttl=55 time=27.754 ms
      64 bytes from 217.137.157.135: seq=33 ttl=55 time=29.883 ms
      64 bytes from 217.137.157.135: seq=34 ttl=55 time=28.041 ms
      64 bytes from 217.137.157.135: seq=35 ttl=55 time=29.877 ms
      64 bytes from 217.137.157.135: seq=36 ttl=55 time=27.763 ms
      64 bytes from 217.137.157.135: seq=37 ttl=55 time=29.648 ms
      64 bytes from 217.137.157.135: seq=38 ttl=55 time=27.820 ms
      64 bytes from 217.137.157.135: seq=39 ttl=55 time=279.683 ms
      64 bytes from 217.137.157.135: seq=40 ttl=55 time=27.552 ms
      64 bytes from 217.137.157.135: seq=41 ttl=55 time=29.928 ms
      64 bytes from 217.137.157.135: seq=42 ttl=55 time=27.534 ms
      64 bytes from 217.137.157.135: seq=43 ttl=55 time=29.630 ms
      64 bytes from 217.137.157.135: seq=44 ttl=55 time=27.609 ms
      64 bytes from 217.137.157.135: seq=45 ttl=55 time=179.461 ms
      64 bytes from 217.137.157.135: seq=46 ttl=55 time=27.618 ms
      64 bytes from 217.137.157.135: seq=47 ttl=55 time=29.438 ms
      64 bytes from 217.137.157.135: seq=48 ttl=55 time=27.588 ms
      64 bytes from 217.137.157.135: seq=49 ttl=55 time=29.468 ms
      64 bytes from 217.137.157.135: seq=50 ttl=55 time=27.384 ms
      64 bytes from 217.137.157.135: seq=51 ttl=55 time=29.488 ms
      64 bytes from 217.137.157.135: seq=52 ttl=55 time=27.391 ms
      64 bytes from 217.137.157.135: seq=53 ttl=55 time=29.445 ms
      64 bytes from 217.137.157.135: seq=54 ttl=55 time=191.312 ms
      64 bytes from 217.137.157.135: seq=55 ttl=55 time=29.246 ms
      64 bytes from 217.137.157.135: seq=56 ttl=55 time=27.409 ms
      64 bytes from 217.137.157.135: seq=57 ttl=55 time=49.207 ms
      64 bytes from 217.137.157.135: seq=58 ttl=55 time=28.619 ms
      64 bytes from 217.137.157.135: seq=59 ttl=55 time=26.782 ms
      64 bytes from 217.137.157.135: seq=60 ttl=55 time=27.910 ms
      64 bytes from 217.137.157.135: seq=61 ttl=55 time=27.526 ms
      64 bytes from 217.137.157.135: seq=62 ttl=55 time=29.890 ms
      64 bytes from 217.137.157.135: seq=63 ttl=55 time=728.035 ms
      64 bytes from 217.137.157.135: seq=64 ttl=55 time=29.859 ms
      64 bytes from 217.137.157.135: seq=65 ttl=55 time=27.813 ms
      64 bytes from 217.137.157.135: seq=66 ttl=55 time=29.907 ms
      64 bytes from 217.137.157.135: seq=67 ttl=55 time=27.707 ms
      64 bytes from 217.137.157.135: seq=68 ttl=55 time=29.910 ms
      ^C
      --- 217.137.157.135 ping statistics ---
      69 packets transmitted, 69 packets received, 0% packet loss

    9. #8
      gymno's Avatar
      gymno Guest
      Exchange:
      Broadband ISP:
      Router:
      Sky TV:

      Re: ping spikes & upstream attenuation halved

      Wow.
      Thanks for taking the time to do all that shonk (aka pingmaster in my house from now on).

      I feel a lot better about my latency now
      And that i'm not with vm. How on earth do they game?

      I notice that in your test the 20ms spike was on line 63, equivalent to test 16 using my draconian method, so it looks like i've nothing to worry about at all....

      As long as my stats stay ok & i don't lose any more speed.

      Thanks again

    10. #9
      Shonk's Avatar
      Shonk is online now Sky User Member
      Exchange:
      Broadband ISP: Sky Fibre Unlimited Pro
      Router: Asus RT-AC88U
      Sky TV: Sky+ HD
      Join Date
      Mar 2010
      Posts
      1,460
      Thanks
      7
      Thanked 118 Times in 113 Posts

      Re: ping spikes & upstream attenuation halved

      That vm ip is host 100% of the time in every game he goes in
      and its the same for all vm users

      thats why cod is so sh1tty it picks on upstream benchmark not latency
      mid game migrations are the only ones that use latency

    11. #10
      gymno's Avatar
      gymno Guest
      Exchange:
      Broadband ISP:
      Router:
      Sky TV:

      Re: ping spikes & upstream attenuation halved

      Another reboot just now & attenuation is back to normal:

      ADSL Link Downstream Upstream
      Connection Speed 19081*kbps 1161*kbps
      Line Attenuation 23.0*dB 14.3*dB
      Noise Margin 7.1*dB 9.0*dB

      Still 1meg down on my downstream sync, but no biggie as long as it doesn't get worse.

      edit: Yes biggie. Got worse.
      Original noise problem is back: lift & shift
      Last edited by gymno; 22-07-12 at 10:14 PM. Reason: update

     

     

    Tags for this Thread

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •  
    SkyUser - Copyright © 2006-2017. SatDish and NewsreadeR | SkyUser is in no way affiliated with Sky Broadband / BSkyB
    RIPA NOTICE: NO CONSENT IS GIVEN FOR INTERCEPTION OF PAGE TRANSMISSION