Jump to content
dedelano

Download Speed Problems

Recommended Posts

Since last Thursday, testmy.net is measuring my speed at half what it had been. I'm pursuing possible issues with Cox, but noticed when one of my applications downloaded an update, my Networx monitor measured it at the speed I expect to get. Is there some issue with testmy.net that would cause my speeds to be cut in half?

David

Share this post


Link to post
Share on other sites

No, but you may have a routing issue that's only effecting curtain sites that you visit.

Here's a random test I just ran.

49YLgGB.png

Cox Communications in Phoenix Arizona, over 1000 miles from TestMy.net's server.

Things are running great on TestMy.net's end. If they weren't I wouldn't be able to max my connection out like that... not to mention all the other users running normal tests (live). Are you experiencing problems anywhere else? Run a traceroute and post your findings...

To run a traceroute...

  • Windows Start > Run > type CMD [enter] > from the command prompt type tracert google.com and/or tracert testmy.net
  • Linux / Mac Under Applications/Utilities open 'Terminal' > type traceroute google.com and/or traceroute testmy.net

Paste those results here.

You definitely have a very abrupt change.

post-2-0-77437700-1317613653_thumb.png

https://testmy.net/stats/?&t=u&d=10022011&x=60&l=100&q=dedelano

Share this post


Link to post
Share on other sites

Here's the tracert, which has some timeouts in it....

Tracing route to testmy.net [174.120.187.140]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1

2 * * * Request timed out.

3 9 ms 8 ms 10 ms 70.169.77.236

4 11 ms 10 ms 10 ms chndcorc01-pos-0-7-0-0.ph.ph.cox.net [70.169.72.58]

5 9 ms 9 ms 9 ms 72.214.144.69

6 22 ms 23 ms 23 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]

7 24 ms 55 ms 35 ms xe-2-3-0.cr1.lax112.us.above.net [64.125.31.190]

8 49 ms 48 ms 53 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]

9 46 ms 47 ms 46 ms xe-1-2-0.cr1.dfw2.us.above.net [64.125.26.129]

10 49 ms 48 ms 47 ms xe-0-1-0.er1.dfw2.us.above.net [64.125.27.74]

11 46 ms 47 ms 49 ms 64.125.199.94.t366.above.net [64.125.199.94]

12 47 ms 45 ms 50 ms te2-2.dsr01.dllstx3.networklayer.com [70.87.255.26]

13 * * * Request timed out.

14 51 ms 52 ms 55 ms a.ff.5746.static.theplanet.com [70.87.255.10]

15 48 ms 47 ms 54 ms 8c.bb.78ae.static.theplanet.com [174.120.187.140]

Trace complete.

I don't know if this comes into play, but I'm using OpenDNS for my DNS service.

BTW, the upload speed comes and goes. I can sometimes reboot the modem and get it back to near 4Mb, but it usually drops back to 1Mb after a while.

David

Share this post


Link to post
Share on other sites

interesting, the first hop outside your LAN is timing out... it could very well be an issue in your neighborhood or your cable modem just not responding to the ICMP packet. the timeout at hop 13 is completely normal btw even my trace has it

Tracing route to testmy.net [174.120.187.140]

over a maximum of 30 hops:

1 8 ms 7 ms 8 ms 10.146.192.1

2 9 ms 18 ms 11 ms 68.2.8.17

3 10 ms 11 ms 9 ms 70.169.75.84

4 12 ms 11 ms 9 ms 72.214.144.69

5 22 ms 23 ms 22 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]

6 43 ms 30 ms 36 ms xe-2-3-0.cr1.lax112.us.above.net [64.125.31.190]

7 48 ms 48 ms 73 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]

8 45 ms 51 ms 70 ms xe-2-1-0.cr1.dfw2.us.above.net [64.125.30.58]

9 46 ms 45 ms 44 ms xe-0-1-0.er1.dfw2.us.above.net [64.125.27.74]

10 48 ms 45 ms 45 ms 64.125.199.94.t366.above.net [64.125.199.94]

11 45 ms 45 ms 46 ms te9-1.dsr01.dllstx3.networklayer.com [70.87.253.6]

12 * * * Request timed out.

13 48 ms 58 ms 54 ms a.ff.5746.static.theplanet.com [70.87.255.10]

14 46 ms 48 ms 47 ms 8c.bb.78ae.static.theplanet.com [174.120.187.140]

Trace complete.

Share this post


Link to post
Share on other sites

interesting, the first hop outside your LAN is timing out... it could very well be an issue in your neighborhood or your cable modem just not responding to the ICMP packet. the timeout at hop 13 is completely normal btw even my trace has it

Tracing route to testmy.net [174.120.187.140]

over a maximum of 30 hops:

1 8 ms 7 ms 8 ms 10.146.192.1

2 9 ms 18 ms 11 ms 68.2.8.17

3 10 ms 11 ms 9 ms 70.169.75.84

4 12 ms 11 ms 9 ms 72.214.144.69

5 22 ms 23 ms 22 ms langbprj01-ae2.rd.la.cox.net [68.1.1.17]

6 43 ms 30 ms 36 ms xe-2-3-0.cr1.lax112.us.above.net [64.125.31.190]

7 48 ms 48 ms 73 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]

8 45 ms 51 ms 70 ms xe-2-1-0.cr1.dfw2.us.above.net [64.125.30.58]

9 46 ms 45 ms 44 ms xe-0-1-0.er1.dfw2.us.above.net [64.125.27.74]

10 48 ms 45 ms 45 ms 64.125.199.94.t366.above.net [64.125.199.94]

11 45 ms 45 ms 46 ms te9-1.dsr01.dllstx3.networklayer.com [70.87.253.6]

12 * * * Request timed out.

13 48 ms 58 ms 54 ms a.ff.5746.static.theplanet.com [70.87.255.10]

14 46 ms 48 ms 47 ms 8c.bb.78ae.static.theplanet.com [174.120.187.140]

Trace complete.

I think that's normal in some cases actually... check out mine.


iMac:~ ca3le$ traceroute testmy.net
traceroute to testmy.net (174.120.187.140), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.434 ms 3.019 ms 1.083 ms
2 * * *
3 ip68-2-1-1.ph.ph.cox.net (68.2.1.1) 10.365 ms 11.534 ms 8.031 ms
4 70.169.75.90 (70.169.75.90) 12.520 ms 9.425 ms 9.313 ms
5 chnddsrj01-ae2.0.rd.ph.cox.net (70.169.76.229) 8.212 ms 9.254 ms 9.960 ms
6 langbprj01-ae2.rd.la.cox.net (68.1.1.17) 22.467 ms 21.371 ms 22.622 ms
7 xe-2-3-0.cr1.lax112.us.above.net (64.125.31.190) 22.417 ms 34.432 ms 22.018 ms
8 xe-3-2-0.cr1.iah1.us.above.net (64.125.26.121) 45.537 ms 55.909 ms 64.033 ms
9 xe-1-2-0.cr1.dfw2.us.above.net (64.125.26.129) 45.468 ms 45.224 ms 48.521 ms
10 xe-0-1-0.er1.dfw2.us.above.net (64.125.27.74) 45.850 ms 66.132 ms 63.610 ms
11 64.125.199.94.t366.above.net (64.125.199.94) 47.191 ms 46.206 ms 48.682 ms
12 te9-1.dsr02.dllstx3.networklayer.com (70.87.253.22) 47.142 ms
te3-5.dsr02.dllstx3.networklayer.com (70.87.253.90) 44.970 ms
te2-2.dsr02.dllstx3.networklayer.com (70.87.255.30) 72.933 ms
13 * * *
14 e.ff.5746.static.theplanet.com (70.87.255.14) 46.685 ms 49.988 ms
a.ff.5746.static.theplanet.com (70.87.255.10) 57.739 ms
15 8c.bb.78ae.static.theplanet.com (174.120.187.140) 45.607 ms 46.678 ms 55.614 ms
[/CODE]

I think that's the router... I'd really like to know why to does that though. Theplanet told me once (why it does it on the host end) but I've forgotten now. :razz:

Share this post


Link to post
Share on other sites

I think that's normal in some cases actually... check out mine.


iMac:~ ca3le$ traceroute testmy.net
traceroute to testmy.net (174.120.187.140), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.434 ms 3.019 ms 1.083 ms
2 * * *
3 ip68-2-1-1.ph.ph.cox.net (68.2.1.1) 10.365 ms 11.534 ms 8.031 ms
4 70.169.75.90 (70.169.75.90) 12.520 ms 9.425 ms 9.313 ms
5 chnddsrj01-ae2.0.rd.ph.cox.net (70.169.76.229) 8.212 ms 9.254 ms 9.960 ms
6 langbprj01-ae2.rd.la.cox.net (68.1.1.17) 22.467 ms 21.371 ms 22.622 ms
7 xe-2-3-0.cr1.lax112.us.above.net (64.125.31.190) 22.417 ms 34.432 ms 22.018 ms
8 xe-3-2-0.cr1.iah1.us.above.net (64.125.26.121) 45.537 ms 55.909 ms 64.033 ms
9 xe-1-2-0.cr1.dfw2.us.above.net (64.125.26.129) 45.468 ms 45.224 ms 48.521 ms
10 xe-0-1-0.er1.dfw2.us.above.net (64.125.27.74) 45.850 ms 66.132 ms 63.610 ms
11 64.125.199.94.t366.above.net (64.125.199.94) 47.191 ms 46.206 ms 48.682 ms
12 te9-1.dsr02.dllstx3.networklayer.com (70.87.253.22) 47.142 ms
te3-5.dsr02.dllstx3.networklayer.com (70.87.253.90) 44.970 ms
te2-2.dsr02.dllstx3.networklayer.com (70.87.255.30) 72.933 ms
13 * * *
14 e.ff.5746.static.theplanet.com (70.87.255.14) 46.685 ms 49.988 ms
a.ff.5746.static.theplanet.com (70.87.255.10) 57.739 ms
15 8c.bb.78ae.static.theplanet.com (174.120.187.140) 45.607 ms 46.678 ms 55.614 ms
[/CODE]

I think that's the router... I'd really like to know why to does that though. Theplanet told me once (why it does it on the host end) but I've forgotten now. :razz:

most routers in my experience don't like to respond to ICMP and even some modems which i think is what his modem is doing on that tracert, i've read places that isps don't like modems to respond to ICMP ping requests

Share this post


Link to post
Share on other sites

it could be a peer issue, myself and a few others are also having issues reaching our max speed, so to avoid the peering/routing issues that can arise CA3LE is in the process of setting up another server for us to test from that is hosted in a different location

edit:

try it out here http://dc.testmy.net/

Share this post


Link to post
Share on other sites

Since last Thursday, testmy.net is measuring my speed at half what it had been. I'm pursuing possible issues with Cox, but noticed when one of my applications downloaded an update, my Networx monitor measured it at the speed I expect to get. Is there some issue with testmy.net that would cause my speeds to be cut in half?

David

Hey David, I just put a new server online in D.C. -- Give it a try and see if your results are any different from the main server....

.... I'm sitting here typing this, then I notice TriRan beat me to it! :icon_thumright:

bah! http://dc.testmy.net/ ! :laughing7:

Share this post


Link to post
Share on other sites

Using the dc.testmy.net site, I'm actually getting faster speeds than I was before. Take a look at my data. I should also note that I was downloading a software update in parallel with this test. I had to use the back button to rerun the test and stay on the dc site, so the slower speeds in the middle are from the original site.

So, what's this mean!?!?!

David

Here's the tracert, just in case...

Tracing route to dc.testmy.net [184.173.139.122]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1

2 * * * Request timed out.

3 8 ms 8 ms 9 ms 70.169.77.236

4 11 ms 10 ms 9 ms chndcorc01-pos-0-7-0-0.ph.ph.cox.net [70.169.72.58]

5 10 ms 11 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]

6 32 ms 33 ms 33 ms 68.1.2.121

7 32 ms 33 ms 33 ms ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]

8 71 ms 67 ms 72 ms ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]

9 69 ms 67 ms 67 ms ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]

10 69 ms 69 ms 68 ms ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]

11 69 ms 69 ms 69 ms po2.fcr03.sr02.wdc01.networklayer.com [208.43.118.159]

12 69 ms 71 ms 69 ms 184.173.139.122-static.reverse.softlayer.com [184.173.139.122]

Trace complete.

Share this post


Link to post
Share on other sites

Any way I can make it "stick" on the dc site? It keeps going to the original site unless I use the back button.

I should have a default option tomorrow.

I went back to my usual automated testing, and all my historical data appears to have been blitzed. I didn't clear cookies or anything. Where did it go??

I'm seeing nearly 2400 results dating back to Mid-May for your username https://testmy.net/quickstats/dedelano

post-2-0-17262400-1317968260_thumb.png

post-2-0-87054000-1317968323_thumb.png

-- if you're not seeing everything it may be because a filter of some sort is on. Clicking the default button will reset your search options.

post-2-0-73286800-1317968261.png

This is because the database search options carry over, so if you search for the past 7 days... next time you load your stats "7 Days" will automatically load for you. When you run the auto test and the test completes it defaults to "1 Day" - it doesn't change that to your default BUT if you happen to query from that page it will set the default to "1" because that's what's entered on that page. Just click default and only the necessary cookies will be reset... I added that button because although that normally saves time, it does sometimes need to be reset.

Share this post


Link to post
Share on other sites

I seem to have all my data back. Not sure what that was all about. I hadn't done anything different. However, Chrome lost it's brain shortly after I started having this problem.

I tried to default to the DC site. You probably know it's not quite working. Yesterday I was getting an endless loop error. Today, I get "The requested URL /tools/test/scheduled.php was not found on this server."

Share this post


Link to post
Share on other sites

I tried to default to the DC site. You probably know it's not quite working. Yesterday I was getting an endless loop error. Today, I get "The requested URL /tools/test/scheduled.php was not found on this server."

D'oh! I renamed that on the main server and forgot to sync the two servers. I'm getting rsync in order so that it's automated from now on.

That was the only problem you had with that server, correct?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...