What happened?

The elapsed “upload time” displayed for uploads includes the initialization time (time spent waiting, signing URLs, etc.) instead of only the actual upload time.

Example scenario: (network adjusted mid-upload)

• File 2GB.txt starts uploading
• File 1GB.txt remains queued while init/URL presigning takes ~45s due to poor network conditions

Expected behavior: At the moment File 1GB.txt starts uploading, its elapsed time should show 0s (count only data transfer).
Actual behavior: When File 1GB.txt begins uploading, the timer already shows ~45s (init/presign time included).

Likely cause: startTime is set when the Observable is created rather than when the first PUT (or first progress event) starts, so initialization time is counted as upload time.

How to reproduce?

1. Upload few large files at once.
2. Wait a bit.

• Under limited resources/network, one file begins uploading while another sits in init/presign, its elapsed time includes the initialization period.
• Alternative: In DevTools, throttle the network to simulate limited resources. The file’s “upload time” increases during init/presign (before the first PUT), so when the upload actually starts it already shows elapsed time.

Version

1.1.0-incubating (Pre-release/Master)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

Chrome

Relevant log output