Internet is back to very high ping + lag again!

So, I posted one similar yesterday and it appeared to have just gone away, however I get on today and the internet is at the laggiest it's been! I really need some help to get rid of this. Any advice please!
Line state:
Connected
Connection time:
0 days, 19:47:15
Downstream:
6.813 Mbps
Upstream:
448 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.1 Annex A
Latency type:
Fast
Noise margin (Down/Up):
4.9 dB / 23.0 dB
Line attenuation (Down/Up):
43.4 dB / 25.0 dB
Output power (Down/Up):
19.9 dBm / 12.1 dBm
FEC Events (Down/Up):
0 / 6
CRC Events (Down/Up):
2760 / 17
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
7254 / 1
Error Seconds (Local/Remote):
1766 / 19
 bttester 
Download - 1.78
upload - 0.05
ping - 200.88

so the problem appears to be with the wifi connection and not the internet as ethernet works ok
you can try downloading inssider3 (istumbler if MAC) and then run it. This will show the broadcasting networks round about you and their channels including your own. If you then enter your router and change your wireless channel to a free or less congested channel.
you can  also change hub from b/g/n to just b/g unless all devices have 'n' wifi cards.  you can also check to make sure your driver is up to date for wifi cards - check manufacturer's website and not rely on windows update
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Similar Messages

  • Very High Ping/Latency

    Good Evening,
    For 4-5 weeks, I have been getting very high pings (>1500ms) this occurs randomly throughout the day and night.
    I have reported a fault and have been told this is normal for peak times.... however they will request a switch over to Fast Path from Interleave.
    Now I'm no Rocket scientist but >1500ms ping in an area with only 200 houses on my exchange IS NOT normal, nor is it even remotely acceptable that i'm told it is!!
    Having browsed the web with this IP (my 1st hop) "217.47.106.122", I find many others with EXACTLY the same issue.
    Please can someone confirm there is an issue with the above address.. 
    My Area Code is 01851 (Isle of Lewis). 
    I am aware there is ongoing work to install infinity on Lewis this summer, yet I haven't been informed of any dissruptions.
    If I was a betting man I'd say many user's have been rerouted and now as a result is being overloaded.. an oversight no doubt.
    Please either confirm this is or at the very least "may" be the case..
    Regards
    Dan 

    Looking good! 
    Tracing route to bbc.co.uk [212.58.246.103]
    over a maximum of 30 hops:
    1 1 ms 1 ms <1 ms BTHomeHub.home [192.168.1.254]
    2 1385 ms 1426 ms 1419 ms 217.47.106.122
    3 783 ms 796 ms 847 ms 217.47.106.193
    4 1024 ms 1004 ms 1069 ms 213.1.69.78
    5 1162 ms 1212 ms 1255 ms 31.55.165.102
    6 1356 ms 1359 ms 973 ms 31.55.165.75
    7 834 ms 847 ms 906 ms 31.55.165.107
    8 1001 ms 1029 ms 1077 ms 109.159.250.52
    9 1218 ms 1278 ms 1222 ms core1-te0-13-0-17.ealing.ukcore.bt.net [109.159.250.42]
    10 1092 ms 703 ms 626 ms peer2-xe0-0-0.telehouse.ukcore.bt.net [109.159.254.102]
    11 644 ms 738 ms 708 ms 194.74.65.42
    12 * * * Request timed out.
    13 1204 ms 1183 ms 1291 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
    14 1228 ms * 690 ms 132.185.255.165
    15 888 ms 904 ms 909 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]
    Trace complete.

  • Slow download, high ping

    Hi
    I'm seeing very slow download speeds and very high ping numbers recently. Mostly evenings. This evening is bad. For example 0.12 mbits download and 2012ms ping. Does anyone have any ideas? I had similar a couple of years ago and it was my profile. But profile is at 7 figure on current Bt wholesale speed tests.

    Thanks, yes results below:
    Download speedachieved during the test was - 0.99 Mbps
     For your connection, the acceptable range of speeds is 0.6 Mbps-7.15 Mbps.
     Additional Information:
     Your DSL Connection Rate :8.13 Mbps(DOWN-STREAM), 0.45 Mbps(UP-STREAM)
     IP Profile for your line is - 7.15 Mbps
    ROUTER DATA&colon;
    Basic Status
    Device Information
    Firmware Version:0.9.1 0.1 v0041.0 Build 140905 Rel.30877n
    Hardware Version:Archer D9 v1 00000000
    System Up Time:0 day(s) 02:08:26
    DSL
    Line Status:Connected
    DSL Modulation Type:ADSL_G.dmt
    Annex Type:Annex A/L
       Upstream DownstreamCurrent Rate (Kbps)Max Rate (Kbps)SNR Margin (dB)Line Attenuation (dB)Errors (Pkts)
    448
    8128
    1140
    11184
    24
    15
    3
    3
    0
    0

  • High Pings, slow performance. Good line stats. P...

    Hi 
    I am suffering from very high ping times and variable download speeds.  I normally get about 15ms ping and 12-15Mb download.  I am currently getting 200-500ms ping times and 1Mb-6Mb download and significant packet loss.  Ping test gives me a server in holland as fastest server!
    My line stats look fine - problem doesn't seem to be the local loop.
    I swapped the ECI modem for a Hauwei from eBay in case that was causing an issue (and so I could access the stats) but it didn't improve things.  Any clue?  Do you know how to get to someone in BT  that I can have a sensible conversation with?  I am preparing myself for the usual long drawn out fight with the helpdesk and hours on the phone.
    1) Exchange and cabinet details
    BT BROADBAND AVAILABILITY CHECKER
    Telephone Number *********** on Exchange HARPENDEN is served by Cabinet 49
    Featured ProductsDownstream Line Rate(Mbps)Upstream Line Rate(Mbps)Downstream Range(Mbps)Availability Date  High Low High Low    
    FTTC Range A (Clean)
    17
    10.6
    1.3
    0.8
    Available
    FTTC Range B (Impacted)
    13.4
    5.3
    1.2
    0.5
    Available
    WBC ADSL 2+
    Up to 2.5
    1 to 4
    Available
    ADSL Max
    Up to 2
    1 to 3.5
    Available
    WBC Fixed Rate

    Available
    Fixed Rate

    Available
    Other Offerings
    FTTP on Demand
    330
    30
    Available
    Fibre Multicast
    Available
    Copper Multicast
    Available
    2) DSL Modem Details
    Device
    Help
    Product type
    EchoLife HG612  
    Device ID
    10C61F-21530315408K25030366
    Hardware version
    VER.B
    Software version
    V100R001C01B030SP08
    Firmware version
    A2pv6C038m.d24j
    Batch number
    BC1P6.030.A2pv6C038m.d24j
    System up time
    0 days 1 hours 18 minutes 15 seconds
    3) DSL Line Stats
    Connection Status
    Help
    Mode
    VDSL2  
    Traffic type
    PTM  
    DSL synchronization status
    Up  
    DSL up time
    0  
    Line Status
    Help
    Downstream
    Upstream
    Attainable rate (kbit/s)
    15524
    1134
    SNR margin (dB)
    30.9
    0
    Line attenuation (dB)
    10.1
    10.5
    Output power (dBmV)
    10.1
    10.5
    Statistics
    Help
    Path 0
    Path 1
    Downstream
    Upstream
    Downstream
    Upstream
    Line rate (kbit/s)
    14999 
    1077 


    CRC errors
    222 
    138 
    18 
    18 
    FEC errors




    HEC errors
    90 
    58 
    32 
    32 
    Thanks for your help!

    Thanks for the quick response!
    BusyBox v1.9.1 (2014-01-21 16:44:38 CST) built-in shell (ash)
    Enter 'help' for a list of built-in commands.
    # xdslcmd info --pbParams
    xdslcmd: ADSL driver and PHY status
    Status: Showtime
    Retrain Reason: 0
    Last initialization procedure status: 0
    Max: Upstream rate = 1134 Kbps, Downstream rate = 15580 Kbps
    Bearer: 0, Upstream rate = 1077 Kbps, Downstream rate = 14999 Kbps
    Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
    Discovery Phase (Initial) Band Plan
    US: (7,32) (871,1205) (1972,2782) 
    DS: (33,859) (1216,1961) (2793,3970) 
    Medley Phase (Final) Band Plan
    US: (7,32) 
    DS: (33,859) 
      VDSL Port Details  Upstream  Downstream
    Attainable Net Data Rate:     1134 kbps     15580 kbps
    Actual Aggregate Tx Power:       10.5 dBm     10.1 dBm
    ==================================================​==================================
    VDSL Band StatusU0U1U2U3U4D1D2D3
      Line Attenuation(dB): 13.4  N/A  N/A  N/A  N/A 28.2 86.8  N/A
    Signal Attenuation(dB): 13.4  N/A  N/A  N/A  N/A 44.8  N/A  N/A
    SNR Margin(dB): 6.8  N/A  N/A  N/A  N/A 6.7  N/A  N/A
    TX Power(dBm): 10.5  N/A  N/A  N/A  N/A 10.1  N/A  N/A

  • Very Slow Internet + High Ping

    I am on a Sager laptop running Windows 7 and using an Airport Extreme Base Station as my router. I don't know how the router is set up or even how to access the router from my computer. My roommate set up the internet before I moved in. I have already contacted my internet provider and they believe my slow service + extremely high pings when I try to play any online game are a result of my router.
    I am just looking for a way to correct my issue. I would also like to know how I can even access my router from my computer. Thanks.

    +Is there any way for the owner of the device to limit the amount of bandwidth I am receiving??+
    No.
    +but I really don't understand why my internet is so crummy.+
    Interference from other wireless networks or cordless phones is usually the cause of issues like this. If you have a cordless phone there, turn it off for an hour or so to see if things improve. Unfortunately, there's not much you can do about a neighbor's cordless phone causing problems or another wireless network.
    +If I could access the utility what would you suggest I check?+
    You can access AirPort Utility by going to the Downloads link on the main forum page. But, you won't be able to access any of the settings on the AirPort Extreme unless you have the device password, which is different than the wireless password. The first thing to do is try different channel settings for the wireless to see if you can find some clear airspace.

  • High Pings and lag in games.

    The problem I have is with gaming early in a morning and towards lunch time are usually fine and late a night into the early hours are usually ok aswell but as soon as peak times roll in my online play is impossible due to high pings and very bad lag, any idea what could be causing my problem please?
    Steps I have taken to date, contact BT and was passed onto tier 2 tech support who then ran a noise check which last 24 hours on my line, which seems to have left my line with a higher noise value than before.
    Tried a different ethernet cable, different micro filter, unplugged everything from the socket except for my Homehub 2, turned off my firewall and virus checker, reset my computer, closed all unused programs. Tried a friends Homehub 2, tried a laptop, all have the same result with high pings and lag in games.
    Also BT quote my line speed should be an estimated 17MB.
    ADSL line status
    Line state
    Connected
    Connection time
    4 days, 22:09:10
    Downstream
    8,128 Kbps
    Upstream
    445 Kbps
    ADSL settings
    VPI/VCI
    0/38
    Type
    PPPoA
    Modulation
    ITU-T G.992.5
    Latency type
    Interleaved
    Noise margin (Down/Up)
    15.6 dB / 30.2 dB
    Line attenuation (Down/Up)
    24.0 dB / 14.1 dB
    Output power (Down/Up)
    0.0 dBm / 10.9 dBm
    Loss of Framing (Local)
    0
    Loss of Signal (Local)
    0
    Loss of Power (Local)
    0
    FEC Errors (Down/Up)
    0 / 0
    CRC Errors (Down/Up)
    3334 / N/A
    HEC Errors (Down/Up)
    N/A / 0
    Error Seconds (Local)
    2211

    Test1 comprises of two tests
    1. Best Effort Test: -provides background information.
    Download  Speed
    6592 Kbps
    0 Kbps
    7150 Kbps
    Max Achievable Speed
     Download speedachieved during the test was - 6592 Kbps
     For your connection, the acceptable range of speeds is 2000-7150 Kbps.
     Additional Information:
     Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 445 Kbps(UP-STREAM)
     IP Profile for your line is - 7170 Kbps
    2. Upstream Test: -provides background information.
    Upload Speed
    363 Kbps
    0 Kbps
    445 Kbps
    Max Achievable Speed
    >Upload speed achieved during the test was - 363 Kbps
     Additional Information:
     Upstream Rate IP profile on your line is - 445 Kbps

  • Response times (PING) very high with CAP3602i access point

    I have installed an access point CAP3602i in mode HREAP a controller Model 5508  with version 7.4.100.0 but the response times of the connected users are very high.
    The less users are connected to the access point is faster surfing the internet and response times are low. But if there are many users connected, increase response times.
    I'll be grateful someone comments any experience with this problem.
    Thanks

    We are talking about 15 users per AP, but that everything is surfing the internet and not so heavy downloads before aps 1141 and had had no such problem response times were normal between 2,3,4 ms
    There is performing some function more cap3602i ap causes high response times.
    Supposedly CAP3602i I say are better than the 1141, which is why we made the change but we found with surprise that high times.
    The SSID was HREAP doubt it has anything to do with the 1141 does not give the issue of high times.

  • Hi, I bought a new Mac Book Pro, very high spec, installed Lion and now the machine is slow, glitchy. how do i wipe it and put Leopard back on it? any help would be great..?

    Hi,
    I bought a new Mac Book Pro a couple of months ago the new model, very high spec, i7 processor, 500g solid state drive, 8 gig of ram. all in all a very fast machine. however, i foolishly downloaded OS X Lion and as soon as i did i noticed a considerable difference in the machine basically its ground to a halt, its now slow glitchy programs shut down and crash. I'm new to Mac and in reminded of life in the world of Windows....! any suggestions should i wipe Lion off the machine and re install Leopard? any help would be appreciated..
    Liam

    Surely you meant to say that there was nothing in Lion you would prefer over !10.6! - Lion is 10.7.
    As for what might be sapping your machines juice - have you run Activity Monitor yet? I always enable 'All Processes' and sort it by %CPU usage if i want to know whats cooking.
    In addition to the list Disk Activity might give a hint.
    If you are quite low on available disk space it might also be that osx is constantly swapping - best to keep a few GB of free space for it to work with.

  • High Packet Loss, High Ping and Slow Connection Ov...

    Hi There,
    I have been a customer with the BT unlimited broadband package for a little under two years and up until recently have had no real issues with the service. This was until around 3/4 weeks ago I noticed that the internet was very slow and certain online games or applications like Netflix would lose all of its quality or stop completely. At first I thought nothing of it and simply reset my BT Home hub router, and sure enough everything was back to normal. However after around 2-3 hours of moderate use (gaming online or watching Netflix) the problem surfaced again.
    Now I am lucky if I can get the entire way through a 40 minute TV episode before the quality drops and/or the service requires buffering. I have already contacted BT via the helpline and the service lady ran through the obligatory steps (turn off, wait 5 minutes, reset the home hub etc.) but she failed to understand that although rebooting the home hub does alleviate the problem initially, the symptoms of a slow connection, high packet loss and high ping always return within an hour.
    Four the last couple of weeks I have been trying to investigate the problem myself and I have done the following things:
    Tested the line using the master socket (no difference)
    Opened the ports on my firewall within the home hub (no difference)
    Directly wired in the computer instead of relying on the wifi (no difference)
    Tested for interference from neighbours wifi using inSSIDider office (it wasn’t, operating on different channels)
    Switched every device that requires internet off apart from the PC (no difference)
    So with all that in mind I am fairly confident that it is nothing within my house that has caused a significant reduction in internet quality.
    Now I have tried my best to display the problem I am having by recording the connection quality for the last 24 hours. The table below represents the condition and quality of the connection after leaving it a period of time without resetting:
    ADSL Line Status
    Connection Information
    Line state:
    Connected
    Connection time:
    0 days, 21:52:14
    Downstream:
    12.96 Mbps
    Upstream:
    910 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.5 Annex A
    Latency type:
    Interleaved
    Noise margin (Down/Up):
    6.7 dB / 5.4 dB
    Line attenuation (Down/Up):
    29.4 dB / 16.4 dB
    Output power (Down/Up):
    20.4 dBm / 12.6 dBm
    FEC Events (Down/Up):
    987297 / 12745
    CRC Events (Down/Up):
    254 / 15268
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    2437 / 252630
    Error Seconds (Local/Remote):
    189 / 36430
    And here is a result of the ping and packet loss during this time:
    Now I immediately reset the home hub after running that test and ran the test again. These are the results I a achieved within 2 minutes of internet connectivity:
    ADSL Line Status
    Connection Information
    Line state:
    Connected
    Connection time:
    0 days, 00:01:05
    Downstream:
    13.77 Mbps
    Upstream:
    910 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.5 Annex A
    Latency type:
    Interleaved
    Noise margin (Down/Up):
    6.4 dB / 5.6 dB
    Line attenuation (Down/Up):
    29.4 dB / 16.4 dB
    Output power (Down/Up):
    20.4 dBm / 12.6 dBm
    FEC Events (Down/Up):
    159 / 12746
    CRC Events (Down/Up):
    1 / 15573
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    0 / 252639
    Error Seconds (Local/Remote):
    1 / 36438
    Even within the time it has taken to compose this page my internet quality has nose-dived from the previous result above to the following: 
    Connection Information
    Line state:
    Connected
    Connection time:
    0 days, 00:52:31
    Downstream:
    13.77 Mbps
    Upstream:
    910 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.5 Annex A
    Latency type:
    Interleaved
    Noise margin (Down/Up):
    6.1 dB / 5.4 dB
    Line attenuation (Down/Up):
    29.4 dB / 16.4 dB
    Output power (Down/Up):
    20.4 dBm / 12.6 dBm
    FEC Events (Down/Up):
    14544 / 12749
    CRC Events (Down/Up):
    14 / 15584
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    72 / 252647
    Error Seconds (Local/Remote):
    10 / 36449
    What is causing this poor quality in connection and what can be done to rectify the problem?
    Thank you for your response in advanced.
    Regards,
    Richard.

    Thank you for you quick reply, I have just moved my hub to the master socket again and re-run the test and I seem to be getting the same results.
    ADSL Line Status
    Connection Information
    Line state:
    Connected
    Connection time:
    0 days, 00:17:47
    Downstream:
    12.96 Mbps
    Upstream:
    910 Kbps
    ADSL Settings
    VPI/VCI:
    0/38
    Type:
    PPPoA
    Modulation:
    G.992.5 Annex A
    Latency type:
    Interleaved
    Noise margin (Down/Up):
    6.0 dB / 5.2 dB
    Line attenuation (Down/Up):
    28.7 dB / 15.9 dB
    Output power (Down/Up):
    20.4 dBm / 12.6 dBm
    FEC Events (Down/Up):
    26417 / 5
    CRC Events (Down/Up):
    1 / 303
    Loss of Framing (Local/Remote):
    0 / 0
    Loss of Signal (Local/Remote):
    0 / 0
    Loss of Power (Local/Remote):
    0 / 0
    HEC Events (Down/Up):
    31 / 11
    Error Seconds (Local/Remote):
    10 / 36522
    I have also checked if the bell wire was attached and it is not. My socket is of the new type with the inclusion of an inductor on the faceplate. My ADSL filters and modem cable already have the middle connecting pins removed so I don’t think it is a wiring problem, at least in my apartment anyway. I have also searched for problems with the exchange and they are showing green for my area. (Liverpool Central)
    I have just rang the quiet line and I do not appear to have any noise on the line. However, all I have is a cordless phone and I know that is not ideal for determining noise due to the radio frequency interfering with the phone speaker.
    Again thank you for you time on this issue.
    Regards,
    Richard

  • BT Infinity 2 and high ping rate

    I am having a problem with my BT Infinity2.  I am getting high ping rates some as high as 181 ms.  I have download speeds of 15 meg and 8-9 meg upload.  This is through the router wired to my computer.  I was told that I should be able to get somewhere in the region of 77 meg.  This is nowhere near and needs to be sorted out.
    It doesn't matter what time of day I do the speed test it is always the same.  If I try and play my Football Manager 2012 game online I can't as my connection just kicks me back off the steam server.  If I try and watch a programme on Iplayer or ITV player ther programmes are fuzzy, blocking and unwatchable, also with the buffering is beyond a joke.

    micksea173 not good and you have my sympathy
    Try rebooting both the hub and the modem. Run the BT Speedtester to get your IP Profiles and  http://www.speedtest.bbmax.co.uk/ to get an accurate speed test. Pings are very dependant on the site you are measuring a ping of 181 for a server in LA could be quite good! If you know how also run a tracert to bbc.co.uk. Post agin with the results and somebody can make an educated guess as to where the problem lies.

  • SG200-26P [FW-1.1.2.0] - Very High Response Time: 1000ms!

    Hello,
    Problem: New SG-200 26P Smart Switch with Latest Firmware - Very High Responce Time 500-800ms
    We've a EdgeMarc 4500 Router with 10 VPN tunnels to 10 brach locations. SG-200 26P Smart Switch is connected to 7 Servers (2 Terminal, SQL, and Other) All locations have 50MB Download and 20MB Upload speed from Verizon FiOS Internet service.
    As per the SolarWind tool, the response time of this switch is around at 500ms. At the same time, the EdgeMarc 4500 router response time is around 40ms and less.
    We've 60 desktops remotely connected to our SQL Server database and 40 RDP Users via Remote Desktop. The configuration is same from past 3 years. But we change the switch from HP 1800-24G to Cisco due to some Connection Failures. For Connection Failures, we first suspect the old HP switch, but it's look like issue with EdgeMarc Router.
    Is this Response Time is normal? I attached two screenshots of both Cisco Switch and EdgeMarc Router Response Time from past 24 hours according to SolarWind tool. Any further advice would be greatly appreciated. Thank you.

    Hello Srinath,
    Thank you for participating in the Small Business support community. My name is Nico Muselle from Cisco Sofia SBSC.
    The response time from the switch could be considered as quite normal. Reason for this is that the switch gives CPU priority to it's actual duties which would of course be switching, access lists, VLANs, QoS, multicast and DHCP snooping etc etc. As a result of that, ping response times of the switch itself do not show in any way the correct working of the switch.
    I invite you to try pinging clients connected to the switch, you should be able to notice that response times to the clients are a lot lower than response times of the switch itself.
    Hope this answers your question !
    Best regards,
    Nico Muselle
    Sr. Network Engineer - CCNA - CCNA Security

  • Slow Speeds/High Ping During Evening

    Just signed up for Comcast this week.  Noticed bad lag while gaming and speed tests indicate slow download speeds (<10 Mbps when I should be getting 75 Mbps) and high ping (200-300ms).  Checked everything hardware related on my end and couldn't find an issue.  Finally, did some trace routing and discovered high ping on Comcast servers in San Jose and Great Oaks.  See tracert results below. These issues seem to occur during the evenings (8pm to midnight PST), but the few checks I did during the day seemed fine.  It may be related to streaming volume at night.  In any event, it's ruining my internet experience.  How can this be resolved? Tracing route to e10905.dspb.akamaiedge.net [23.211.8.171]
    over a maximum of 30 hops:1 1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
    2 14 ms 11 ms 10 ms 98.207.208.1
    3 13 ms 18 ms 10 ms te-0-7-0-17-sur03.pleasanton.ca.sfba.comcast.net
    [68.86.142.189]
    4 16 ms 12 ms 14 ms 162.151.78.209
    5 25 ms 13 ms 30 ms be-101-ar01.santaclara.ca.sfba.comcast.net [68.8
    5.154.105]
    6 * * * Request timed out.
    7 317 ms 305 ms 305 ms be-10910-cr01.sanjose.ca.ibone.comcast.net [68.8
    6.86.102]
    8 501 ms * 452 ms be-14-pe02.11greatoaks.ca.ibone.comcast.net [68.
    86.83.34]
    9 356 ms 305 ms 305 ms a23-211-8-171.deploy.static.akamaitechnologies.c
    om [23.211.8.171]Trace complete.C:\Users\Derek>tracert google.comTracing route to google.com [74.125.239.96]
    over a maximum of 30 hops:1 1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
    2 10 ms 9 ms 9 ms 98.207.208.1
    3 10 ms 13 ms 9 ms te-0-7-0-17-sur03.pleasanton.ca.sfba.comcast.net
    [68.86.142.189]
    4 17 ms 11 ms 13 ms 162.151.78.209
    5 18 ms 14 ms 22 ms be-101-ar01.santaclara.ca.sfba.comcast.net [68.8
    5.154.105]
    6 * * * Request timed out.
    7 189 ms 255 ms 250 ms he-0-10-0-0-pe02.529bryant.ca.ibone.comcast.net
    [68.86.86.26]
    8 229 ms 337 ms 418 ms 66-208-228-70.ubr01a.hurtl301.al.hfc.comcastbusi
    ness.net [66.208.228.70]
    9 236 ms 305 ms 305 ms 72.14.232.138
    10 213 ms 218 ms 187 ms 66.249.95.29
    11 194 ms 286 ms 321 ms nuq05s01-in-f0.1e100.net [74.125.239.96]Trace complete.C:\Users\Derek>tracert google.comTracing route to google.com [216.58.192.46]
    over a maximum of 30 hops:1 1 ms <1 ms 1 ms router.asus.com [192.168.2.1]
    2 14 ms 10 ms 9 ms 98.207.208.1
    3 14 ms 9 ms 10 ms te-0-7-0-17-sur03.pleasanton.ca.sfba.comcast.net
    [68.86.142.189]
    4 15 ms 11 ms 17 ms 162.151.78.209
    5 17 ms 13 ms 13 ms be-101-ar01.santaclara.ca.sfba.comcast.net [68.8
    5.154.105]
    6 * * * Request timed out.
    7 427 ms 305 ms 304 ms he-0-14-0-1-pe03.11greatoaks.ca.ibone.comcast.ne
    t [68.86.86.202]
    8 210 ms 305 ms 304 ms 173.167.59.66
    9 479 ms 305 ms 305 ms 209.85.241.55
    10 282 ms 305 ms 304 ms 74.125.37.43
    11 215 ms 305 ms 304 ms nuq04s30-in-f14.1e100.net [216.58.192.46]Trace complete.

    The same thing is happening for me. I live in Houston, Texas and my ping to a game called LoL was around 80 now its at 90. It's not a huge difference and I don't notice anything when gaming. I'm just curious as to why this has happened? 

  • Extremely high ping times only fixed via restart

    I have 2 BR350 in bridge to a remote tower that has an AP350 providing access to customers. The customers will call in with complaints of very slow access. I have been onsite to see that a user can login to the AP350(web) fine but the BR350 at the tower is slow and the BR350 at the far tower is for most purposes dead. The link still shows up around 65% to 75% signal strength. By restarting either BR350 the link will come back fine. I have been using Ping Plotter to keep track of the ping times and see that the response times sometime slow grow or instantly grow to around 2000ms to 4000ms. Ping times from the customer to the AP350 on the tower remain below 10ms during all of this.
    I have had a similar problem with an AP350 in another city thats ping time do the same thing and require a reboot. It's ping time from the client side can range form 4ms to 800ms on regular usage as well. This customer has an average of 80% signal strength from the Workgroup Bridge.
    How can I find out what is causing that strange high ping time on these situations.
    All units running firmware 12.00
    Thanks for the help.
    MV

    Normally ,the first thing to do is to check the software version used. Here,in your case you are using the latest software release(12.00T). So now the problem can be isolated to other issues. Bridge software provides tools to show you the types of problems and where the bridge is encountering the problems. Two of the most helpful tools are the Throughput statistics and the Error statistics screen.You can get the procedure for collecting the error statistics using the following URLs:
    http://www.cisco.com/warp/public/102/wlan/br-ts-22950.shtml#conn
    http://www.cisco.com/warp/public/102/wlan/errors.html

  • Extremely high ping times ( 3000ms) and unusable ...

    Hi all,
    I am currently at my girlfriends house, trying to do some work but am experiencing absolutely dreadful internet connectivity.
    I have just setup a small *nix box plugged directly into the HH4's gigabit ethernet port purely to monitor this abysmal connectivity. Due to the super high latency and low bandwidth for upload / downloads our internet is virtually unusable.
    Here are a couple of excerpts from this mornings logged data.
    Firstly latency of 4129.204 ms!!!
    23/06/15 : 09:09
    ./speedtest-cli
    Retrieving speedtest.net configuration...
    Retrieving speedtest.net server list...
    Testing from BT (86.165.237.95)...
    Selecting best server based on latency...
    Hosted by Spectrum Internet (Cardiff) [90.75 km]: 4129.204 ms
    Testing download speed........................................
    Download: 0.10 Mbit/s
    Testing upload speed..................................................
    Upload: 0.10 Mbit/s
    Secondly ping test to bbc.co.uk again showing very high and varied latency. Avg 1629.844ms  high 2361.604ms
    PING bbc.co.uk (212.58.244.18) 56(84) bytes of data.
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=1 ttl=50 time=653 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=2 ttl=50 time=730 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=3 ttl=50 time=1188 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=4 ttl=50 time=1529 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=5 ttl=50 time=1464 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=6 ttl=50 time=600 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=7 ttl=50 time=153 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=8 ttl=50 time=491 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=9 ttl=50 time=148 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=10 ttl=50 time=870 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=11 ttl=50 time=1163 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=12 ttl=50 time=1202 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=13 ttl=50 time=1192 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=14 ttl=50 time=1209 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=15 ttl=50 time=1193 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=16 ttl=50 time=644 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=17 ttl=50 time=139 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=18 ttl=50 time=96.6 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=19 ttl=50 time=158 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=20 ttl=50 time=510 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=21 ttl=50 time=653 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=22 ttl=50 time=613 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=23 ttl=50 time=827 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=24 ttl=50 time=829 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=25 ttl=50 time=922 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=26 ttl=50 time=124 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=27 ttl=50 time=94.0 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=28 ttl=50 time=90.9 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=29 ttl=50 time=419 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=30 ttl=50 time=364 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=31 ttl=50 time=358 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=32 ttl=50 time=361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=33 ttl=50 time=402 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=34 ttl=50 time=382 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=35 ttl=50 time=427 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=36 ttl=50 time=409 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=37 ttl=50 time=443 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=38 ttl=50 time=566 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=39 ttl=50 time=651 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=40 ttl=50 time=580 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=41 ttl=50 time=205 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=42 ttl=50 time=361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=43 ttl=50 time=372 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=44 ttl=50 time=386 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=45 ttl=50 time=360 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=46 ttl=50 time=381 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=47 ttl=50 time=419 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=48 ttl=50 time=430 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=49 ttl=50 time=408 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=50 ttl=50 time=409 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=51 ttl=50 time=492 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=52 ttl=50 time=709 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=53 ttl=50 time=817 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=54 ttl=50 time=1073 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=55 ttl=50 time=1373 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=56 ttl=50 time=1197 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=57 ttl=50 time=1406 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=58 ttl=50 time=1565 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=59 ttl=50 time=1714 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=60 ttl=50 time=1835 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=61 ttl=50 time=2018 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=62 ttl=50 time=2151 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=63 ttl=50 time=2237 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=64 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=65 ttl=50 time=2295 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=66 ttl=50 time=2300 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=67 ttl=50 time=2311 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=68 ttl=50 time=2329 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=69 ttl=50 time=2352 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=70 ttl=50 time=2323 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=71 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=72 ttl=50 time=2236 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=73 ttl=50 time=2257 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=74 ttl=50 time=2224 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=75 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=76 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=77 ttl=50 time=2247 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=78 ttl=50 time=2258 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=79 ttl=50 time=2237 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=80 ttl=50 time=2251 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=81 ttl=50 time=2341 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=82 ttl=50 time=2330 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=83 ttl=50 time=2257 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=84 ttl=50 time=2319 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=85 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=86 ttl=50 time=2278 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=87 ttl=50 time=2361 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=88 ttl=50 time=2341 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=89 ttl=50 time=2306 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=90 ttl=50 time=2358 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=91 ttl=50 time=2328 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=92 ttl=50 time=2252 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=93 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=94 ttl=50 time=2248 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=95 ttl=50 time=2302 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=96 ttl=50 time=2322 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=97 ttl=50 time=2281 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=98 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=99 ttl=50 time=2295 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=100 ttl=50 time=2277 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=101 ttl=50 time=2244 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=102 ttl=50 time=2256 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=103 ttl=50 time=2253 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=104 ttl=50 time=2244 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=105 ttl=50 time=2252 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=106 ttl=50 time=2291 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=107 ttl=50 time=2245 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=108 ttl=50 time=2309 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=109 ttl=50 time=2299 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=110 ttl=50 time=2313 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=111 ttl=50 time=2300 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=112 ttl=50 time=2286 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=113 ttl=50 time=2254 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=114 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=115 ttl=50 time=2242 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=116 ttl=50 time=2246 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=117 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=118 ttl=50 time=2251 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=119 ttl=50 time=2253 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=120 ttl=50 time=2219 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=121 ttl=50 time=2210 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=122 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=123 ttl=50 time=2261 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=124 ttl=50 time=2228 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=125 ttl=50 time=2274 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=126 ttl=50 time=2265 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=127 ttl=50 time=2255 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=128 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=129 ttl=50 time=2248 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=130 ttl=50 time=2274 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=131 ttl=50 time=2282 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=132 ttl=50 time=2283 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=133 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=134 ttl=50 time=2270 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=135 ttl=50 time=2273 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=136 ttl=50 time=2192 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=137 ttl=50 time=2304 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=138 ttl=50 time=2296 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=139 ttl=50 time=2284 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=140 ttl=50 time=2270 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=141 ttl=50 time=2272 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=142 ttl=50 time=2263 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=143 ttl=50 time=2305 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=144 ttl=50 time=2283 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=145 ttl=50 time=2250 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=146 ttl=50 time=2266 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=147 ttl=50 time=2269 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=148 ttl=50 time=2247 ms
    64 bytes from fmt-vip72.telhc.bbc.co.uk (212.58.244.18): icmp_seq=149 ttl=50 time=2267 ms
    ^C
    --- bbc.co.uk ping statistics ---
    151 packets transmitted, 149 received, 1% packet loss, time 150279ms
    rtt min/avg/max/mdev = 90.912/1629.844/2361.604/830.792 ms, pipe 3

    Anyone able to advise what to do about this problem?

  • High ping on Valve servers

    Hi,
    Over the past month or so, ive noticed im getting a ping of over 200 on Valve servers on Team Fortess 2. For the past 2 weeks, it seemed to had settled down a little to about 70 ping, which i can play on but now its back to 200+. After starting a steam forum thread about this, i soo realised that everyone that has the problem is on BT infinity. One guy added me and we discussed what we was on and what problems we were getting and they were identical. BT Homehub 4, high ping only on Valve servers
    Ive reset my connection in a million different ways suggested by different people and none of that did anything. From a few searches, some people fixed the issue by getting mods to change their latency type from Interleaved to Fast, but i dont know what im on so i cant tell if thats the issue.
    I dont know what im meant to post but this is all the specs under "Helpdesk":
    1. Product name:
    BT Home Hub
    2. Serial number:
    +068341+NQ31327903
    3. Firmware version:
    Software version 4.7.5.1.83.8.130.1.17 (Type A) Last updated 10/05/14
    4. Board version:
    BT Hub 4A
    5. WAN:
    PPP Connected
    6. Data sent/received:
    136.1 MB / 415.5 MB
    7. Broadband username:
    [email protected]
    8. BT FON:
    Yes
    9. 2.4 GHz Wireless network/SSID:
    BTHub4-XS3P
    10. 2.4 GHz Wireless connections:
    Enabled (802.11 b/g/n (Recommended)) 20 MHz, WPS enabled
    11. 2.4 GHz Wireless security:
    WPA and WPA2
    12. 2.4 GHz Wireless channel:
    Automatic / 11
    13. 5 GHz Wireless network/SSID:
    BTHub4-XS3P
    14. 5 GHz Wireless connections:
    Enabled (802.11 n 40 MHz (Recommended)) 20/40 MHz, WPS enabled
    15. 5 GHz Wireless security:
    WPA2
    16. 5 GHz Wireless channel:
    Automatic / 40
    17. Firewall:
    Default
    18. MAC Address:
    2c:39:96:6b:7d:56
    19. Software variant:
    20. Boot loader:
    BT Home Hub 4 (Type A) | Software version 4.7.5.1.83.8.130.1.17 | Last updated 10/05/14
    Any help?

    Just got off the phone with someone from BT trying to convince me its an issue either my end or Valve's end (Even though it happens on non valve games also). Valve have told me its my ISP, which i am 100% certain it is, and she is just telling me to reset my router just once more.
    Hope the forum can save me here

Maybe you are looking for