Ok, so that works, a timeout based on bottom speed of 960 kilobits comes out at 170 seconds, for the 20MB file so 10 seconds grace on the 3 mins. However, speaking for myself, I have a 500 kilobit upload, and around 5Mb download. So that means I'm only ever going to be able to upload a ~10.9MB file before I hit the timeout. Are those of us stuck with poor internet connections going to be screwed? Do you really need such a tight timeout on the upload? However, as I commented in the post earlier today, I'm not even getting that far. My upload is terminating after ~36s, again no error just progress stops and I can see the TX stops from my machine. It doesn't explain the mismatch of data sent vs the progress bar either. In 36s @ 500 kilobits I could only have TX'd 2250k of the 9100k file, yet the progress bar shows ~46% of 9100k which is around 4186k. So something else is clearly broken here. Stephanie B. said: Hi, Dresdon, Sorry for the miscommunication-- that should have said 120 kB/s-- it's in kilobytes, not kilobits. In kilobits, it's 960 kilobits/sec. I've updated the comment above and will update the release notes as well. The timeout starts after the spinner stops and when the progress bar begins-- that's when the file is actually being transferred. Before that, the file is being processed locally. Just looking at your comment of 120kb/s and a 3m timeout. when does that kick in? Unless I'm misunderstanding something here. 120 kilobit transmission for 3 minutes is 21600 kilobits, so 2.7 Megabytes, which is well short of the 20 Megabyte file size limit. Surely to allow a 20 Megabyte file to upload at 120 kilobit/s you'd need a timeout in the order of: 20MB = 20480KB = 163840 kilobits @ a rate of 120 kilobits/s you'd need ~1365 seconds or ~23 minutes. Is there a confusion here about storage in Mega/Kilo bytes and transmission in kilo bits?