Can someone upload a large file to this FTP for me?

[Trevelyan]

I am having some FTP issues, and want to see if there are any problems elsewhere in the world. I'm thinking that my ISP (Cox) is throttling my FTP connection, which is causing me to have constant disconnect/reconnect issues.... I want to see if anyone else is experiencing this.

Please upload a file (larger than 10mb or so) and tell me:

1. Where you're located
2. About how fast it went
3. Your ISP

Thanks! Let me know any problems...

209.59.146.4
u: test@designbygraphite.com
p: test

 

[Red Squirrel]

Woah that's really good speed tbh. Getting 600kb/sec or so. Definably not speed I get at home. (uploading from corporate network)

 

[Trevelyan]

Thanks man! What is your ISP?

The reason I ask is if I connect to the FTP via 209.59.146.4 (like you did) I get slow speeds and disconnects. BUT, if I connect to my server via 209.59.146.5 (different IP, same destination) I get 500kb/s steady, no problems.

I'm thinking that maybe Cox or some connection along the way is throttling the FTP bandwidth for that IP address only... is something like that possible? I've tested from several locations.... same problem, but only on Cox business internet. On Cox Home its fine...

 

[xSauronx]

are you running any other heavy uploads or QoS on your end that could slow things down? what kind of upload speed is your connection rated for?

 

[Red Squirrel]

hmm not even sure what ISP we're going through. Either Bell or HydroOne. It's a dedicated line, not res internet.

I'm in Timmins, ON, Canada

 

[Trevelyan]

are you running any other heavy uploads or QoS on your end that could slow things down? what kind of upload speed is your connection rated for?

Nope, I'm the only one uploading anything right now. It's a 2Mb/s up connection, Cox Business.

What's so weird is, like I said, if I use the ".4" ip address it stalls and disconnects, but if I use the ".5" it goes through fine, at 300kb/s pretty constant (just checked).

I have a service call in with Cox to check if their routing is messed up.

 

[Nuwave]

I attempted to Download "file.txt"
1st try I got disconncted after downloading 2KB.
2nd try I downloaded around 300KB/s got about 60% done and got disconnected
3rd try I downloaded at over 360KB/s completed succesfully

Upload same file back as "file2.txt"
1st try @ over 560KB/s

My ISP is Group Telecom out of Calgary Alberta, Canada. Supposidly the bandwidth is 25Mbps up/25Mbps down.

I deleted File2.txt when i was done.

 

[Trevelyan]

I just restarted the FTP service... so that's probably why you got disconnected the first times....

But for me, I can't upload anything for more than a few seconds before it freezes.... tried a couple different computers, both at work and at a friend's office with the same result.

 

[Trevelyan]

Okay, I can DOWNLOAD fine at around 1.2mb/s... but uploading stops after maybe 1-2 seconds.

What in the world would cause that except for an ISP issue? Maybe upstream capping for my IP address?

 

[Nuwave]

Are your computers located at the same place as the FTP server? Or is that hosted somewhere else by a third party?

I'll try the download again.

152.042 seconds, 336.75 Kbytes per second. 1st try.

 

[Trevelyan]

Server is a dedicated hosted by Liquidweb.com... They assure me everything is fine on thier end. Several businesses now have told me they are having the same problem... They are all located in my town.

 

[Nuwave]

Server is a dedicated hosted by Liquidweb.com... They assure me everything is fine on thier end. Several businesses now have told me they are having the same problem... They are all located in my town.

If they all have the Same ISP, it would diffinately point towards an issue there. Which you have already put a call in for. Good luck.

 

[Trevelyan]

Here's a tracert:

Tracing route to www.[removed].org [209.59.146.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.101.1
2 7 ms 7 ms 8 ms 10.16.46.1
3 13 ms 10 ms 9 ms ip68-1-11-9.at.at.cox.net [68.1.11.9]
4 66 ms 8 ms 7 ms ftwlcmtc04.at.at.cox.net [68.1.10.226]
5 35 ms 33 ms 31 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
6 25 ms 26 ms 26 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
04.146]
7 33 ms 35 ms 35 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
.29]
8 56 ms 57 ms 57 ms cr1-pos-0-7-5-0.chicago.savvis.net [204.70.194.5
0]
9 56 ms 57 ms 60 ms ber1-te-1-0-0.chicagoequinix.savvis.net [204.70.
196.22]
10 56 ms 57 ms 57 ms 209.176.218.106
11 67 ms 67 ms 67 ms lw-dc2-core4-te9-1.rtr.liquidweb.com [209.59.157
.226]
12 71 ms 58 ms 59 ms lw-dc2-sec3-dist5-po2.rtr.liquidweb.com [209.59.
157.120]
13 61 ms 58 ms 59 ms host.designbygraphite.com [209.59.146.4]

Trace complete.


When I run it on my Mac the #6-10 just show *'s and take a few seconds on each one.... Could it be a problem on those routers at Savvis?

 

[gsaldivar]

I'm seeing some major packet loss problems to that IP. Haven't tried the upload though:

http://just-ping.com/index.php?vh=209.59.146.4&c=&s=ping!

 

[Zoomer]

To the .4

227 Entering Passive Mode (209,59,146,4,161,184)
150 Accepted data connection
226-File successfully transferred
226 81.989 seconds (measured here), 1.28 Mbytes per second
110366720 bytes sent in 82 seconds (1.3e+03 Kbytes/s)

To the .5

227 Entering Passive Mode (209,59,146,5,216,86)
150 Accepted data connection
226-File successfully transferred
226 81.072 seconds (measured here), 1.30 Mbytes per second
110366720 bytes sent in 81 seconds (1.3e+03 Kbytes/s)

Doesn't look like there is any significant difference. This is from the planet.

--> The ftp daemon doesn't support ls and rm doesn't delete files.

 

[somethingsketchy]

Thanks man! What is your ISP?
I'm thinking that maybe Cox or some connection along the way is throttling the FTP bandwidth for that IP address only... is something like that possible? I've tested from several locations.... same problem, but only on Cox business internet. On Cox Home its fine...

It is certainly possible that Cox is throttling the connection (they certainly have the right to do so, if the overall network traffic is being consumed by a few bandwidth hogs), but since you mentioned that you were only getting 500KB/s that is probably not the case. That aside, the disconnects are probably something to do with the Cox Business Internet package (maybe the Terms Of Service do not allow FTP connections on a corporate/business connection(s)).

Have you contacted customer service/technical support about this problem? A quick conversation with them, could clear this issue up, or simply reconfirm what kind of restrictions you have a business Internet connection.

Hope that helps.

 

[Trevelyan]

It is certainly possible that Cox is throttling the connection (they certainly have the right to do so, if the overall network traffic is being consumed by a few bandwidth hogs), but since you mentioned that you were only getting 500KB/s that is probably not the case. That aside, the disconnects are probably something to do with the Cox Business Internet package (maybe the Terms Of Service do not allow FTP connections on a corporate/business connection(s)).

Have you contacted customer service/technical support about this problem? A quick conversation with them, could clear this issue up, or simply reconfirm what kind of restrictions you have a business Internet connection.

Hope that helps.

They told me they didn't throttle FTP connections, but he took all my information and said he would talk to the Engineers. That was on Friday. I'm hoping I hear back from them on Monday.

Honestly, I don't mind throttling, as long as it still WORKS!

 

[Henderson]

I used to have this exact problem with my isp, Earthlink, where I could never upload anything other than tiny files without it timing out. The problem was the MTU setting needed to be changed from 1500 to 1492. You might try it (or the reverse if you're already at 1492) if nothing else is helping. Or go through the steps to figure out what your ideal MTU setting would be.

 

[Trevelyan]

I used to have this exact problem with my isp, Earthlink, where I could never upload anything other than tiny files without it timing out. The problem was the MTU setting needed to be changed from 1500 to 1492. You might try it (or the reverse if you're already at 1492) if nothing else is helping. Or go through the steps to figure out what your ideal MTU setting would be.

Well, the reason I'm sure it's not a problem on my end is that:

1) It worked fine until last Wednesday, and we made no changes.
2) Two other IP addresses that point to the same server work... it's only this one that is having trouble.
3) FTP in general is fine. I can upload to all the servers I've tested, just not this particular IP address.

It leads me to believe it got flagged, or somehow the routing got messed up.

 

[Emulex]

you sure they just don't have a bad route going on? trace the AS (BGP) i've seen some whacky stuff lately - florida to dallas to atlanta - perhaps they have one of those gubment systems capturing your data and making things slower.

try this:
ftp 1,2,3,4,5..10 files at once? does the bandwidth degrade as a total? no explanation but i've seen a bad route (or router? or port) cause this anomaly where you could get 150k/sec per ftp session; whereas I could push 1500k/sec with one session