[HSI] Download slower than upload?

[HSI] Download slower than upload?
Links: home · search · speed test · login · more ·

Links: Reply New Topic
Forums » US Cable Support » Patriot Media » [HSI] Download slower than upload?

altimac @ 1st Mar 12:21PM:
[HSI] Download slower than upload?

Got a weird issue here, hoping someone can help. I have a Web server colocated in Vegas, been using it for 3 yrs. now and I have Patriot HSI, 7/1 service. Since February 20, download speeds from my server in Vegas to my network here at home have dropped from 3-4Mbps on average to 100K-300K. What's weird is that all my friends and clients are seeing 3000K-7000K when I have them run the speed test I set up on the server. When I do the patmedia.net speed test I get 10Mbps easily, sometimes as high as 11Mbps. So Patmedia tech support says nothing's wrong.
Other thing is, when I remote into my server and ping my own IP here (24.225.160.118) the ping is normal (75ms on average) but I can't complete a traceroute back to my IP. My speed test is at

»server.altimac.com/speedtest

Would appreciate anyone who's listening giving it a try if only to see if I'm crazy or not...

Here's the traceroute from my server back to me:

Traceroute has started ...

traceroute to 24.225.160.118 (24.225.160.118), 64 hops max, 40 byte packets
1 cust-66.116.103.1.switchcommgroup.com (66.116.103.1) 1.053 ms 0.450 ms 0.390 ms
2 cust-66.209.87.229.switchcommgroup.com (66.209.87.229) 0.248 ms 0.379 ms 0.222 ms
3 2g.po2.trix01.las.switchcommgroup.com (66.209.64.113) 0.588 ms 0.319 ms 0.256 ms
4 66.186.192.45 (66.186.192.45) 0.333 ms 0.434 ms 0.363 ms
5 66.186.192.194 (66.186.192.194) 6.318 ms 6.265 ms 6.221 ms
6 ge-2-1-0.mpr2.lax2.us.above.net (198.32.146.44) 6.360 ms 6.397 ms 6.336 ms
7 so-0-1-0.mpr3.lax9.us.above.net (64.125.30.125) 6.713 ms 6.565 ms 6.551 ms
8 so-0-1-0.mpr3.iah1.us.above.net (64.125.25.46) 39.360 ms 48.517 ms 39.359 ms
9 so-0-0-0.mpr4.iah1.us.above.net (64.125.26.14) 41.760 ms 39.247 ms 62.003 ms
10 so-1-1-0.mpr2.dca2.us.above.net (64.125.28.49) 64.776 ms 64.186 ms 64.613 ms
11 so-0-1-0.mpr2.lga5.us.above.net (64.125.26.106) 67.543 ms 67.622 ms 67.503 ms
12 reserved.above.net.48.184.208.in-addr.arpa (208.184.48.198) 69.050 ms 68.739 ms 68.776 ms
13 g-6-1.hlb-c4.patmedia.net (24.225.237.194) 69.397 ms 68.845 ms 68.917 ms
14 g-2-0-0.hlb-k1.patmedia.net (24.225.237.238) 68.941 ms 68.920 ms 68.772 ms
15 * * *
reply

anon @ 3rd Mar 09:16PM:
Re: [HSI] Download slower than upload?

I'm seeing about 250k here.. thats awfully slow. I assume the reason for the slow down is because we are now using comcast's backbones.
reply

altimac @ 3rd Mar 09:54PM:
Re: [HSI] Download slower than upload?

Thanks for checking. I hope that's not what we have to look forward to from Comcast. I'm hoping that they really do come through with the DOCSIS 3 modems by end of year as some people are claiming they will.
reply

DaveNJ @ 4th Mar 09:27AM:
Re: [HSI] Download slower than upload?

i am not betting on Doc3, or tru2way. The way comcast upsets its customers. They will be lucky to retain half of there customers in the old patriot service area.
reply

fbnpro @ 27th Mar 05:49AM:
Re: [HSI] Download slower than upload?

My servers are hosted in Texas, California and Virgina since the switch I have the same problem it is a very high chance (my way of saying I am sure) that it is the new backbone. In fairness to PatMedia/Comcast they have a lot of problems once the connection leaves Metro NYC ring they use, ping your server from different points or different backbones like I have and you will see what I mean.

Your connection shows locally whatever they want but try infospeed.verizon.net and you will see something much different. Need to find the test site I used in the past when I actually believed they (Patmedia) cared about it...will update.

Gene
reply

altimac @ 28th Mar 05:22AM:
Re: [HSI] Download slower than upload?

Strangely enough, this issue finally cleared up a couple weeks ago when a very helpful tech at Patriot forced me onto a different subnet from which to grab a dynamic IP. From that point on it's been fine. So whatever subnet I was using before had some bizarre routing problems that my current IP range (24.225.176.x) does not.
reply