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

    Page 3 of 6 FirstFirst 12345 ... LastLast
    Results 21 to 30 of 51
    Like Tree1Likes

    Pings & G.INP

    This is a discussion on Pings & G.INP within the Sky Broadband help forums, part of the Sky Broadband help and support category; Originally Posted by Scubbie Stranger and stranger. 30ms is 'normal' for Sky ADSL Broadband, so even 27ms is technically alright. ...

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

      Re: Pings & G.INP

      Quote Originally Posted by Scubbie View Post
      Stranger and stranger.

      30ms is 'normal' for Sky ADSL Broadband, so even 27ms is technically alright.

      15ms was exceptional.
      It still is.
      It's the change around with each new ip address i'm given that's freaky.

      Google.com:
      PING 173.194.34.168 (173.194.34.168): 56 data bytes
      56 bytes from 173.194.34.168: icmp_seq=0 ttl=59 time=15.5 ms
      56 bytes from 173.194.34.168: icmp_seq=1 ttl=59 time=15.0 ms
      56 bytes from 173.194.34.168: icmp_seq=2 ttl=59 time=15.3 ms
      56 bytes from 173.194.34.168: icmp_seq=3 ttl=59 time=15.3 ms

      --- 173.194.34.168 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 15.0/15.2/15.5 ms

      ^ Was 27ms up until 1pm today.

      For the record, these are my pings to the bqm, which ties in with the current graph:

      PING 80.249.99.164 (80.249.99.164): 56 data bytes
      56 bytes from 80.249.99.164: icmp_seq=0 ttl=60 time=27.4 ms
      56 bytes from 80.249.99.164: icmp_seq=1 ttl=60 time=27.4 ms
      56 bytes from 80.249.99.164: icmp_seq=2 ttl=60 time=27.5 ms
      56 bytes from 80.249.99.164: icmp_seq=3 ttl=60 time=27.5 ms

      --- 80.249.99.164 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 27.4/27.4/27.5 ms
      Last edited by gymno; 21-06-14 at 12:07 AM.


    2. Advertisement
    3. #22
      Saturday's Avatar
      Saturday is offline Sky User Super Mod
      Exchange:
      Broadband ISP: Sky Broadband Unlimited Pro
      Router: Sky Hub SR102
      Sky TV: Sky+HD box
      Join Date
      Sep 2006
      Posts
      6,086
      Thanks
      20
      Thanked 52 Times in 47 Posts

      Re: Pings & G.INP

      I recall something similar years back with Sky BB. There were certain IP ranges that performed much better than others* so if you got an affected one you'd reboot again (and again**) until you got into a "good" range. I don't recall that the reason was ever known but the supposition was that it had to do with routing issues. Following a network upgrade the problem disappeared.

      Out of interest you might consider doing a traceroute each time your IP and/or latency changes. You may see a correlation with IP/routing.


      * not for everyone on that range though. It seemed to be location related i.e. where you were on the network topography
      ** no DLM issues in those days

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

      Re: Pings & G.INP

      Yay.
      Just noticed a 6ms drop on my bqm graph.
      So pinged the other 6 benchmark addresses i use & they're all back to 15 or 16ms too.

      The only other time that's happened since january when the weirdness started, was for the first 2 hours or so after the major southeast outage on 4th may was fixed.
      That was during a period where not all sites were reachable yet & the network was still getting up & running.

      Fingers crossed.
      Attached Thumbnails Attached Thumbnails Pings & G.INP-b1aa7b63cb19f65d5e1b243c68c5b92a.jpg  

    5. #24
      Scubbie's Avatar
      Scubbie is online now Sky User Moderator
      Exchange: 02392
      Broadband ISP: Sky Fibre Unlimited
      Router: Sky Q Hub ER110
      Sky TV: Sky+HD box
      Join Date
      Mar 2010
      Location
      Near Portsmouth
      Posts
      27,894
      Thanks
      810
      Thanked 2,194 Times in 2,064 Posts

      Re: Pings & G.INP

      I'm sure that someone can arrange to correct that for you.

      I've arranged for some thunderstorms in you local area. It's all random of course, but one just might get you cabinet .

      Sky Fibre Unlimited Pro: Connected at 80,000 kbps / 20,000 kbps
      Previous ADSL2+ Speed 19999 kbps 1153 kbps, Line Attenuation 17.5 db 6.9 db, Noise Margin 7.5 dB 8.7 dB
      Speedtest: 17.15MB/s 0.97Mb/s Ping 31 ms

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

      Re: Pings & G.INP

      The normality lasted about 4 1/2 hours.

      6ms jump on the bqm graph at 4:15am & benchmark addresses are all back to either 15, 21 or 27ms again, so yet another false alarm.

      Strangely, 4 1/2 hours is usually the length of time between the regular phantom events that show up on my bqm graph when the connection isn't being used.

      Not today though.
      There's more activity than usual between 6 & 7:45am + another little bit at 9am, all of which occurred while i wasn't even home.
      Wireless is disabled with just a ps3 & sky box connected (pushed on demand turned off).

      Spooky.
      Attached Thumbnails Attached Thumbnails Pings & G.INP-b1aa7b63cb19f65d5e1b243c68c5b92a.jpg  

    7. #26
      Shonk's Avatar
      Shonk is offline 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: Pings & G.INP

      My father's ADSL 2+ Line still seems to be on fastpath

      From His Adsl 2+ Line
      root@Nas:~# ping 173.194.34.168
      PING 173.194.34.168 (173.194.34.168): 56 data bytes
      64 bytes from 173.194.34.168: seq=0 ttl=58 time=11.674 ms
      64 bytes from 173.194.34.168: seq=1 ttl=58 time=11.488 ms
      64 bytes from 173.194.34.168: seq=2 ttl=58 time=11.425 ms
      64 bytes from 173.194.34.168: seq=3 ttl=58 time=11.817 ms
      ^C
      --- 173.194.34.168 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 11.425/11.601/11.817 ms

      From My FTTC Line
      PING 173.194.34.168 (173.194.34.168): 56 data bytes
      64 bytes from 173.194.34.168: seq=0 ttl=58 time=9.943 ms
      64 bytes from 173.194.34.168: seq=1 ttl=58 time=9.796 ms
      64 bytes from 173.194.34.168: seq=2 ttl=58 time=9.898 ms
      64 bytes from 173.194.34.168: seq=3 ttl=58 time=9.836 ms
      ^C
      --- 173.194.34.168 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 9.796/9.868/9.943 ms

      From me to him
      PING 2.120.59.14* (2.120.59.14*): 56 data bytes
      64 bytes from 2.120.59.14*: seq=0 ttl=62 time=8.298 ms
      64 bytes from 2.120.59.14*: seq=1 ttl=62 time=8.013 ms
      64 bytes from 2.120.59.14*: seq=2 ttl=62 time=8.539 ms
      64 bytes from 2.120.59.14*: seq=3 ttl=62 time=8.344 ms
      64 bytes from 2.120.59.14*: seq=4 ttl=62 time=8.353 ms
      ^C
      --- 2.120.59.14* ping statistics ---
      5 packets transmitted, 5 packets received, 0% packet loss
      round-trip min/avg/max = 8.013/8.309/8.539 ms

    8. #27
      Isitme's Avatar
      Isitme is offline Sky User Moderator
      Exchange: Bannockburn
      Broadband ISP: Sky Fibre Unlimited
      Router: Sky Hub SR102
      Sky TV: Sky+ HD
      Join Date
      Dec 2006
      Location
      Central Scotland
      Posts
      34,131
      Thanks
      64
      Thanked 1,641 Times in 1,602 Posts

      Re: Pings & G.INP

      Although not as good as that, mine is now the best its ever been so something has been done -

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

      C:\Windows\system32>ping 173.194.34.168

      Pinging 173.194.34.168 with 32 bytes of data:
      Reply from 173.194.34.168: bytes=32 time=18ms TTL=58
      Reply from 173.194.34.168: bytes=32 time=18ms TTL=58
      Reply from 173.194.34.168: bytes=32 time=18ms TTL=58
      Reply from 173.194.34.168: bytes=32 time=18ms TTL=58

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

      C:\Windows\system32>

      TomD


      Please note the views and recommendations in my posts are my own and in no way reflect the views of SkyUser.


      Useful Utilites

      http://www.nirsoft.net/utils/wifi_information_view.html/ TCPOptimiser /Test Socket

      Note - When downloading always select the Custom install or you will end up with stuff you don't want.





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

      Re: Pings & G.INP

      My baseline is still 15ms, so can't complain about that.

      PING 4.69.153.134 (4.69.153.134): 56 data bytes
      56 bytes from 4.69.153.134: icmp_seq=0 ttl=59 time=15.2 ms
      56 bytes from 4.69.153.134: icmp_seq=1 ttl=59 time=15.0 ms
      56 bytes from 4.69.153.134: icmp_seq=2 ttl=59 time=15.3 ms
      56 bytes from 4.69.153.134: icmp_seq=3 ttl=59 time=15.3 ms

      The google.com address from Isitme's post:

      PING 173.194.41.64 (173.194.41.64): 56 data bytes
      56 bytes from 173.194.41.64: icmp_seq=0 ttl=59 time=27.4 ms
      56 bytes from 173.194.41.64: icmp_seq=1 ttl=59 time=27.6 ms
      56 bytes from 173.194.41.64: icmp_seq=2 ttl=59 time=26.4 ms
      56 bytes from 173.194.41.64: icmp_seq=3 ttl=59 time=26.9 ms

      The google.com address my router's dns lookup gives:

      PING 173.194.34.168 (173.194.34.168): 56 data bytes
      56 bytes from 173.194.34.168: icmp_seq=0 ttl=59 time=22.1 ms
      56 bytes from 173.194.34.168: icmp_seq=1 ttl=59 time=22.9 ms
      56 bytes from 173.194.34.168: icmp_seq=2 ttl=59 time=23.0 ms
      56 bytes from 173.194.34.168: icmp_seq=3 ttl=59 time=22.1 ms

      When you consider that prior to january (& for 4 1/2 hours last night) all these addresses + some others i use to test were at 15ms, it is a little odd isn't it?
      Also, if i were to reboot the router now for a new ip address, these figures would all switch around.

    10. #29
      Saturday's Avatar
      Saturday is offline Sky User Super Mod
      Exchange:
      Broadband ISP: Sky Broadband Unlimited Pro
      Router: Sky Hub SR102
      Sky TV: Sky+HD box
      Join Date
      Sep 2006
      Posts
      6,086
      Thanks
      20
      Thanked 52 Times in 47 Posts

      Re: Pings & G.INP

      A ping result is affected by many things:
      • the device's connection to the router e.g. ethernet, powerline or wireless
      • the line/network protocols e.g. interleave, fastpath
      • the connection routing e.g. distance* and number of hops to destination

      etc

      If you find your pings change with a change of IP address that is probably down to a routing change.


      * signals are travelling at near light speed so distance in this context is geographic i.e. where in the world is the server you are pinging, not how long your line is to the exchange.

    11. #30
      Scubbie's Avatar
      Scubbie is online now Sky User Moderator
      Exchange: 02392
      Broadband ISP: Sky Fibre Unlimited
      Router: Sky Q Hub ER110
      Sky TV: Sky+HD box
      Join Date
      Mar 2010
      Location
      Near Portsmouth
      Posts
      27,894
      Thanks
      810
      Thanked 2,194 Times in 2,064 Posts

      Re: Pings & G.INP

      Just for comparison I've done these using the SR101's tool to ping:

      PING 4.69.153.134 (4.69.153.134): 56 data bytes
      64 bytes from 4.69.153.134: seq=0 ttl=59 time=10.635 ms
      64 bytes from 4.69.153.134: seq=1 ttl=59 time=10.939 ms
      64 bytes from 4.69.153.134: seq=2 ttl=59 time=11.015 ms
      64 bytes from 4.69.153.134: seq=3 ttl=59 time=11.051 ms

      --- 4.69.153.134 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 10.635/10.910/11.051 ms

      PING 173.194.41.64 (173.194.41.64): 56 data bytes
      64 bytes from 173.194.41.64: seq=0 ttl=59 time=10.523 ms
      64 bytes from 173.194.41.64: seq=1 ttl=59 time=10.011 ms
      64 bytes from 173.194.41.64: seq=2 ttl=59 time=10.244 ms
      64 bytes from 173.194.41.64: seq=3 ttl=59 time=10.295 ms

      --- 173.194.41.64 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 10.011/10.268/10.523 ms

      PING 173.194.34.64 (173.194.34.64): 56 data bytes
      64 bytes from 173.194.34.64: seq=0 ttl=59 time=10.230 ms
      64 bytes from 173.194.34.64: seq=1 ttl=59 time=9.930 ms
      64 bytes from 173.194.34.64: seq=2 ttl=59 time=9.977 ms
      64 bytes from 173.194.34.64: seq=3 ttl=59 time=10.238 ms

      --- 173.194.34.64 ping statistics ---
      4 packets transmitted, 4 packets received, 0% packet loss
      round-trip min/avg/max = 9.930/10.093/10.238 ms

      To be fair the only way I'm going to improve this would be to have FTTP or move to a location much closer to Sky's servers.

      I have seen someone's pings consistently better than my own and they live in London.

      Sky Fibre Unlimited Pro: Connected at 80,000 kbps / 20,000 kbps
      Previous ADSL2+ Speed 19999 kbps 1153 kbps, Line Attenuation 17.5 db 6.9 db, Noise Margin 7.5 dB 8.7 dB
      Speedtest: 17.15MB/s 0.97Mb/s Ping 31 ms

     

     
    Page 3 of 6 FirstFirst 12345 ... LastLast

    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