Slow Internet Speeds

Discussion in 'Software' started by Adrynalyne, Jun 15, 2004.

  1. Adrynalyne

    Adrynalyne Guest

    My ISP wants me to gather info for them on how sucky my 1.5/1.5 connection has been, so I can preferably roll my service into 1.5mbit DSL...

    Houston, we have a problem...

    I have ping tests too.
     
  2. Adrynalyne

    Adrynalyne Guest

    Tower

    10:13 PM
    Mon 06/14/2004


    Pinging 216.183.67.126 with 1472 bytes of data:



    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=35ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=34ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=36ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=34ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=33ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=58ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=34ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=34ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=36ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=52ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=26ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=34ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=59ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=61ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=81ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=25ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=70ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=56ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=59ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=57ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=25ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=54ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=48ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=27ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=64ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=56ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=49ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=24ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=54ms TTL=255

    Reply from 216.183.67.126: bytes=1472 time=30ms TTL=255



    Ping statistics for 216.183.67.126:

    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 24ms, Maximum = 81ms, Average = 38ms

    Looks good here

    DNS server
    10:13 PM
    Mon 06/14/2004


    Pinging 216.183.68.110 with 1472 bytes of data:



    Reply from 216.183.68.110: bytes=1472 time=312ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=253ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=274ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=192ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=271ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=369ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=422ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=286ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=239ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=138ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=86ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=153ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=128ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=125ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=93ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=104ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=162ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=275ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=357ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=350ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=302ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=133ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=134ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=198ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=164ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=233ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=230ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=222ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=295ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=297ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=429ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=453ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=328ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=259ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=419ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=276ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=345ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=176ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=241ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=334ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=244ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=194ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=277ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=244ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=304ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=154ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=295ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=253ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=269ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=168ms TTL=126



    Ping statistics for 216.183.68.110:

    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 86ms, Maximum = 453ms, Average = 249ms

    Stupid DNS server

    Thing is though, I had Dantekgeek ping the same and get better results. So its NOT just the DNS server. He is in Colorado, Im less than 30 miles away.
     
  3. Adrynalyne

    Adrynalyne Guest

    Here is another, keep in mind this is supposed to be 1.5/1.5:
     
  4. alanc

    alanc MajorGeek

    That sucks big time.

    Not that many years ago a T1 (that actually did 1.5/1.5) was fine for a 100+ node network.
     
  5. DavidGP

    DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

    Dunno what I can do to help you out with that one mate, it seems to be giving you random low figures, you used another bandwith speed test?


    Just humour me and have ago with this one from the other side of the globe from you, Im just curious to hat it will give you.......... http://www.starman.ee/starmankodu/index.php?id=500

    Click Test > a new 1/3 size window will apear on the left just wait and it will give your download speed once its finished in a lovely shade of pink!
    sorry its not in english.
     
  6. Adrynalyne

    Adrynalyne Guest

    Well, Im using that particular test at that site (lax.speakeasy.net) per ISP request.

    The ping test to my local DNS server is obnoxious too.

    It cleared up almost 10 hours later...

    :mad:
     
  7. DavidGP

    DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

    I have had similar in the past speeds slow as a slug, then a day later ok.... DNS servers updating prehaps?
     
  8. Adrynalyne

    Adrynalyne Guest

    So my ISP upgraded the tower bandwidth today.

    Lookie what I traded high latency for!

    07:00 PM
    Wed 06/23/2004


    Pinging 216.183.68.110 with 1472 bytes of data:



    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=49ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=167ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=49ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=114ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=97ms TTL=126

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=43ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=88ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=50ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=95ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=43ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=97ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=99ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=52ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=70ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=46ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=103ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=73ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=105ms TTL=126

    Request timed out.

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=47ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=133ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=68ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=148ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=43ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=53ms TTL=126

    Request timed out.

    Reply from 216.183.68.110: bytes=1472 time=46ms TTL=126

    Reply from 216.183.68.110: bytes=1472 time=42ms TTL=126



    Ping statistics for 216.183.68.110:

    Packets: Sent = 50, Received = 34, Lost = 16 (32% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 42ms, Maximum = 167ms, Average = 69ms
     
  9. InYearsToCome

    InYearsToCome MajorGeek

    wheres this test located? I'm assuming its not a bad score from California...

    Line speed is 3.4/256k
     

    Attached Files:

  10. nickson2

    nickson2 Master Sergeant

    Heres mine, im in uk and its supposed to be 756K does it look ok?
     

    Attached Files:

  11. Adrynalyne

    Adrynalyne Guest

    Think about it.

    The tower is my default gateway.

    The DNS servr is local.

    What is there to trace?

    These are tests they requested.

    I think they mean a lot.
     
  12. Adrynalyne

    Adrynalyne Guest

    There is one machine between my DNS server and the tower.

    The problem at this point begins at the tower.

    There is nothing to trace. That one machine between my tower and DNS server will not be causing the problem, if the problem begins there.

    You also have to understand, my ISP can send packets from my antenna to the raido tower and DNS server just like if they were sitting at the bridge at home.

    They actually see the problem as well, which is why they aren't fighting back very hard. These tests aren't even needed, IMO.
    If that one machine between my tower and primary DNS server made a difference, they would have asked me to do a trace to it.

    Sorry if I sound a little cranky, but this is something I have done my homework on.

    Take a look for yourself, Kaula.
    http://www.gci-net.com/users/s/silver256/

    All tests can be downloaded in zip format. They include screenshots of bandwidth tests.
     
  13. Adrynalyne

    Adrynalyne Guest

    Yes...
     
  14. Adrynalyne

    Adrynalyne Guest


    The other thing here is that is not my job to prove to them where exactly the problem lies, but merely to prove that is a local problem on their servers and not a problem further down on the backbone. If its a backbone problem, I am SOL.

    If the problem exists getting to their DNS server, its certainly not Sprint's problem. (I think thats who they still use). ANd it most certainly is not a problem with my machine, either. See what I am getting at?
     
  15. Adrynalyne

    Adrynalyne Guest

    Look how crappy my upload is to my webspace.

    This is a 260kb file.

    It timed out after about 10 minutes.
     
  16. Adrynalyne

    Adrynalyne Guest

    No problem. Sorry, I'm a little touchy on this because I've been dealing with this for so long.

    Hopefully today I find out if my drop my contract so I can get DSL.
     
  17. Adrynalyne

    Adrynalyne Guest

    Stupid edit timer...

    That was supposed to say:

    Hopefully today I find out if my ISP will drop my contract so I can get DSL.
     
  18. Adrynalyne

    Adrynalyne Guest

    I've apparently missed posts in this thread. Sorry :(

    In no particular order:

    Halo:

    My ISP has local bandwidth tests now. They are showing similar results.

    InYearsToCome:

    The ping tests are local servers. The tower, can be seen from my house. Thats how close I am to it.
     
  19. Adrynalyne

    Adrynalyne Guest

    Update.

    It appears we have a resolution. My wife called today, with the intent of killing someone ;)

    So, here is the breakdown of what they offerred to us.

    Fee to break contract >waived
    Fee to setup DSL >waived
    This month bill >waived
    We should be getting DSL within two weeks.
    They also are looking into letting us keep the wireless until Novemeber, along WITH the DSL and see which works better.

    My ISP has redeemed itself so far :D :D
     
  20. alanc

    alanc MajorGeek

    That's good news man ;)
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds