Internet bandwith maxed after streaming video.

Almost every time I stream video online my bandwith maxes out after just a few minutes and streaming comes to a crawl. I have not noticed any trends with different players/websites, they all generally seem to do it. When I open up Task Manager nothing is using any bandwith, yet pages load extremely slow. Additionally my AV tells me how much I'm using up/down and it is maxed. If I restart my PC it works fine.

I have a 3Mb/s connection.
Here is a pic of my AV telling me I'm basically maxing my connection, along with speedtest and Network Resource Monitor.
http://i55.tinypic.com/2435gcm.png

Any help would be amazing, this has been bugging me forever and I can't figure it out.
38 answers Last reply
More about internet bandwith maxed streaming video
  1. pay for a better connection,, 1 of my local ISPs (the one i use) has something called turbo boost, it'll bump you up to higher service level for first 3 MB then drop you down to your regular level,, it'll affect your connection for sure.
    3mb/s is slow to stream, but if you have tried several sites including youtube and all have the issue, it is your speed.
    i run a 25mb/s connection and never have a streaming issue unless i am d/l over 2000 kps which would mean your 500 kps is too slow.
  2. A slow connection wouldn't explain why it is still maxed even after streaming.

    Unfortunately I can't upgrade unless I switch ISP, but I have bundles with Verizon. Trying to hold out for fios.
  3. install the network monitor gadget addgadget.com to assist on this issue, bring up your task manager and end each process till your network usage drops to identify the culprit.
    maybe it is something trying to do updates that is triggered from the media streaming for some reason or another.
  4. monkeysweat said:
    install the network monitor gadget addgadget.com to assist on this issue, bring up your task manager and end each process till your network usage drops to identify the culprit.
    maybe it is something trying to do updates that is triggered from the media streaming for some reason or another.


    Went ahead and tried that but it didn't do anything for me. Closed everything and eventually got to critical processes like explorer and had to restart. No change in speed.
  5. Are you sure you don't have a virus? What AV program are you using and have you tried scanning it with a different one?
  6. try changing your DNS servers to opendns
    i've had a slow (dropping) DNS before and it murders web browsing and streaming
    you can find the DNS ips for opendns on their website

    if its still an issue after that;
    stream a video get to the 'slowness'
    close out of any applications you have open, including AV

    open cmd and do a netstat

    see if you can find your culprit there
  7. codemastadink said:
    Went ahead and tried that but it didn't do anything for me. Closed everything and eventually got to critical processes like explorer and had to restart. No change in speed.

    i'm not surprised pc crashed, would be expected as you will hit some critical programs, just start from the other end of list, if you do all of them, I'll be out of guesses as to what is wrong.
  8. ninesunz said:
    try changing your DNS servers to opendns
    i've had a slow (dropping) DNS before and it murders web browsing and streaming
    you can find the DNS ips for opendns on their website



    Sorry man I'm super terrible with networking. Any way you could break that down like I was a six year old?
  9. assuming you're using a router for your internet connection

    go into the router setup and for the DNS entries use;

    208.67.222.222
    208.67.220.220

    apply; this will restart your router and it will be about a minute until your PC gets an IP address from your router.
  10. ninesunz said:
    assuming you're using a router for your internet connection

    go into the router setup and for the DNS entries use;

    208.67.222.222
    208.67.220.220

    apply; this will restart your router and it will be about a minute until your PC gets an IP address from your router.


    Alright so it should look like this?

    http://i56.tinypic.com/2ut40ud.png
  11. yes, now you can check to see if the DNS took by opening command prompt and typing in;

    ipconfig /all

    you'll need to find the entry that says;

    Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2011 6:49:21 PM
    Lease Expires . . . . . . . . . . : Sunday, September 17, 2147 1:29:46 AM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 208.67.222.222
    208.67.220.220

    if your DNS serves show the opendns IPs it is set properly
  12. ninesunz said:
    yes, now you can check to see if the DNS took by opening command prompt and typing in;

    ipconfig /all

    you'll need to find the entry that says;

    Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2011 6:49:21 PM
    Lease Expires . . . . . . . . . . : Sunday, September 17, 2147 1:29:46 AM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 208.67.222.222
    208.67.220.220

    if your DNS serves show the opendns IPs it is set properly


    Looks like it didn't. Still has them as 192.168.1/2
  13. the DNS servers?
    192.168.1 would be a LAN address

    run ipconfig /all and post it here
  14. ninesunz said:
    the DNS servers?
    192.168.1 would be a LAN address

    run ipconfig /all and post it here



    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : TP-LINK 150Mbps Wireless Lite N Adapter
    Physical Address. . . . . . . . . : D8-5D-4C-8B-6C-E1
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::3d51:8fc5:794b:cf61%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.24(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 332946764
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BE-62-A6-6C-62-6D-05-A9-AC

    DNS Servers . . . . . . . . . . . : 192.168.1.1
    192.168.1.2
    NetBIOS over Tcpip. . . . . . . . : Enabled
  15. yeah the DNS servers is all wrong, i dont see how you're using the internet at all

    direct your browser to 192.168.1.1
    log into your router

    find the page where you setup your connection, in there should be a place for you to set your DNS servers
  16. ninesunz said:
    yeah the DNS servers is all wrong, i dont see how you're using the internet at all

    direct your browser to 192.168.1.1
    log into your router

    find the page where you setup your connection, in there should be a place for you to set your DNS servers


    I don't understand. I did that before ( http://i56.tinypic.com/2ut40ud.png ) and you said it was correct.
  17. is your router a modem and router built into one?
  18. ninesunz said:
    is your router a modem and router built into one?


    Yes
  19. that's going to be a pain.

    let's check somthing else out first.
    get to where you can't stream anymore or its really slow

    then open command prompt and type in;

    ping google.com -n 100

    post your results
  20. C:\Users\Cody>ping google.com -n 100
    Ping request could not find host google.com. Please check the name and try again
    .

    C:\Users\Cody>ping google.com -n 100

    Pinging google.com [74.125.224.50] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=309ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=375ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=210ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=373ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=279ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=623ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=534ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=483ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=648ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=1661ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=561ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=488ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1329ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=772ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=675ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=224ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=284ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=416ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=603ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=644ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=553ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=750ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1482ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=659ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1213ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=605ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1157ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=507ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=760ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1023ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1289ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1248ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1723ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1867ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=869ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1153ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1421ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=597ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=634ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=752ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=864ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=602ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=595ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=2673ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=1533ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=1304ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=1026ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=796ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=1152ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=36ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=64ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=432ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=391ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=548ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=521ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=728ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=523ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=834ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=668ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=856ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=914ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=138ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=255ms TTL=56

    Ping statistics for 74.125.224.50:
    Packets: Sent = 100, Received = 66, Lost = 34 (34% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 2673ms, Average = 747ms

    C:\Users\Cody>ping g
  21. perhaps try to update your network chip driver?
  22. monkeysweat said:
    perhaps try to update your network chip driver?


    Network chip driver? If you mean the wireless usb adapter that I use, I've already done that :/
  23. try going wired and see if you get same issue,,, may be the adapter
  24. do;

    nslookup

    and post results
  25. C:\Users\Cody>nslookup
    DNS request timed out.
    timeout was 2 seconds.
    Default Server: UnKnown
    Address: 192.168.1.1
  26. i'm guessing it shoud give you 192.168.1.1 as an address.

    next lets set your network adaptor DNS settings to OPENDNS

    right click network > properties > 'change adaptor settings' on the left

    right click your wireless adaptor > properties > double click the TCP/IPv4

    on the bottom click 'use the following DNS server address'

    type in
    208.67.222.222
    208.67.220.220

    open a command prompt

    type ipconfig /flushdns

    type ipconfig /all

    look for DNS entry, it should now have the OPENDNS numbers
  27. oops after typing in the OPENDNS numbers
    208.67.222.222
    208.67.220.220

    hit okay and exit out of the network adaptor settings
  28. C:\Users\Cody>ipconfig /flushdns

    Windows IP Configuration

    Successfully flushed the DNS Resolver Cache.

    C:\Users\Cody>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Cody-PC
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : TP-LINK 150Mbps Wireless Lite N Adapter
    Physical Address. . . . . . . . . : D8-5D-4C-8B-6C-E1
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::3d51:8fc5:794b:cf61%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.24(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 332946764
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BE-62-A6-6C-62-6D-05-A9-AC

    DNS Servers . . . . . . . . . . . : 208.67.222.222
    208.67.220.220
    NetBIOS over Tcpip. . . . . . . . : Enabled


    Looks good then? Should hopefully fix it? I'll try and see if it does it.
  29. try running
    ping google.com -n 100

    see if you get better results
  30. or see if your video streaming is any better
  31. oh also do

    nslookup

    it should return the OPENDNS entry
  32. ninesunz said:
    try running
    ping google.com -n 100

    see if you get better results



    So I opened a few videos and it jumped up, closed them and it remained laggy for a bit and it showed that I was maxing my bandwidth. Figured it didn't help but then it dropped back down to normal. I guess I'll play around with it some more and see: here is the ping results:

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

    C:\Users\Cody>ping google.com -n 100

    Pinging google.com [74.125.224.50] with 32 bytes of data:
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=365ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=363ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=676ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=220ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=306ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=222ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=306ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=222ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=305ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=221ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=316ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=217ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=317ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=247ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=228ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=290ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=245ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=273ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=402ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=275ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=189ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=261ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=262ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=248ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=279ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=412ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=609ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=406ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=239ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=310ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=246ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=279ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=252ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=280ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=296ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=253ms TTL=56
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=227ms TTL=56
    Request timed out.
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=306ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=223ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=315ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=243ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=309ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=39ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=39ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=39ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=35ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=36ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=36ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=39ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Request timed out.
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=39ms TTL=56
    Reply from 74.125.224.50: bytes=32 time=36ms TTL=56

    Ping statistics for 74.125.224.50:
    Packets: Sent = 100, Received = 74, Lost = 26 (26% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 676ms, Average = 184ms


    Looks a lot better. Hopefully it stays this way.
  33. C:\Users\Cody>nslookup
    Default Server: resolver1.opendns.com
    Address: 208.67.222.222

    >
  34. Looks like it started slow and got better

    ~40ms isn't bad

    remember to nslookup to confirm you're on OPENDNS's DNS

    right now you're using the adaptor to force over to OPENDNS, if you could figure out how to set the DNS on your router it would be optimal. Unfortunitly i'm not familiar with those westells
  35. you could also try a

    tracert google.com

    do that a coulpe times and you should see where its slowing down
  36. I'll try and look into changing it on the router. Here is trace route results. idk what it means really but you might see something usefull ;P

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

    C:\Users\Cody>tracert google.com

    Tracing route to google.com [74.125.224.51]
    over a maximum of 30 hops:

    1 * 3 ms 3 ms 192.168.1.1
    2 27 ms 27 ms 26 ms L100.LSANCA-DSL-64.verizon-gni.net [173.58.250.1
    ]
    3 57 ms 27 ms 26 ms G0-3-0-6.LSANCA-LCR-22.verizon-gni.net [130.81.1
    36.182]
    4 27 ms 27 ms 33 ms so-4-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
    .151.248]
    5 33 ms 30 ms 29 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
    6 30 ms 29 ms 29 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
    7 29 ms 30 ms 28 ms TenGigE0-7-2-0.GW4.LAX15.ALTER.NET [152.63.114.2
    29]
    8 83 ms 84 ms 84 ms google-gw.customer.alter.net [63.125.112.154]
    9 28 ms 28 ms 29 ms 216.239.46.40
    10 39 ms 40 ms 38 ms 64.233.174.207
    11 * 39 ms 40 ms 209.85.250.61
    12 37 ms 36 ms 39 ms 64.233.174.15
    13 40 ms 38 ms 37 ms 64.233.174.15
    14 37 ms 38 ms 38 ms 74.125.224.51

    Trace complete.

    C:\Users\Cody>tracert google.com

    Tracing route to google.com [74.125.224.51]
    over a maximum of 30 hops:

    1 2 ms 1 ms 1 ms 192.168.1.1
    2 30 ms 29 ms 27 ms L100.LSANCA-DSL-64.verizon-gni.net [173.58.250.1
    ]
    3 27 ms 34 ms 27 ms G0-3-0-6.LSANCA-LCR-22.verizon-gni.net [130.81.1
    36.182]
    4 28 ms 28 ms * so-4-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
    .151.248]
    5 29 ms 29 ms 30 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
    6 29 ms 29 ms 29 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
    7 28 ms 29 ms 28 ms TenGigE0-7-1-0.GW4.LAX15.ALTER.NET [152.63.114.2
    25]
    8 80 ms 81 ms 81 ms google-gw.customer.alter.net [63.125.112.154]
    9 28 ms 28 ms 29 ms 216.239.46.40
    10 39 ms 40 ms 39 ms 64.233.174.207
    11 39 ms 42 ms 39 ms 209.85.250.61
    12 38 ms 40 ms 38 ms 64.233.174.15
    13 39 ms 38 ms * 64.233.174.15
    14 135 ms 109 ms 106 ms 74.125.224.51

    Trace complete.

    C:\Users\Cody>tracert google.com

    Tracing route to google.com [74.125.224.50]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 26 ms 26 ms 26 ms L100.LSANCA-DSL-64.verizon-gni.net [173.58.250.1
    ]
    3 28 ms 30 ms 28 ms G0-3-0-6.LSANCA-LCR-21.verizon-gni.net [130.81.1
    36.180]
    4 28 ms 30 ms 29 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
    .29.124]
    5 28 ms 28 ms 29 ms 0.so-1-3-0.XL3.LAX15.ALTER.NET [152.63.114.145]

    6 28 ms 28 ms 28 ms 0.so-7-1-0.XL3.LAX15.ALTER.NET [152.63.1.226]
    7 83 ms 79 ms 83 ms google-gw.customer.alter.net [63.125.112.154]
    8 83 ms 84 ms 86 ms google-gw.customer.alter.net [63.125.112.154]
    9 29 ms 29 ms 29 ms 64.233.174.190
    10 39 ms 40 ms 40 ms 64.233.174.205
    11 39 ms 40 ms 41 ms 209.85.250.61
    12 41 ms 41 ms 40 ms 209.85.250.65
    13 * 38 ms 36 ms 74.125.224.50

    Trace complete.

    C:\Users\Cody>
  37. everything seems normal, are your videos still laggy?
  38. My AV still has my bandwidth jumping up and down after I stream something but it doesn't seem to be effecting it as much. So far it looks like it has at least improved a good bit. I guess I'll keep an eye on it over the next few days and see how it goes.
Ask a new question

Read More

Streaming Video Internet Windows 7