Upload and download times depend on your connection, your device and the files being transferred. Check whether the transfer is progressing or showing an error before starting it again.
Check the transfer
On desktop, open Hivenet and note the transfer status or error. If your version shows Syncing or Issues, check those views.
In the web app, check the upload's progress and any error shown. Keep the tab open while the transfer runs.
For automatic photo uploads, check Photo Backup and its own status.
For Send, keep the original sending tab open until the upload finishes and the transfer is ready.
If a Store upload has failed or a visible file will not download, record the exact message and contact Support with the details below. Keep the original file and any device where it still opens.
Check the conditions
Confirm that the device is connected to the internet. Note whether other online tasks are slow too.
Check whether other large transfers or demanding apps are using the connection or device.
Check available device space before downloading. Account storage and device storage are separate.
Note how many files are involved and their total size. A collection of small files can behave differently from one large file.
An internet speed test is useful context, but its result is not a promised Hivenet transfer speed. Avoid repeatedly restarting an active transfer just because it is taking longer than expected.
Check whether the rate is shown in MB/s or Mbps before comparing it with a speed test. These use bytes and bits respectively. See storage sizes and transfer units.
Check the result
Note the time, file count, size and progress shown. Check again to see whether progress changes or an error appears. After a Store upload finishes, download a separate copy and open it. For a downloaded file, check its contents before treating the transfer as complete.
If it stays slow
Check Send browser guidance if the problem is in Send. For help with an ongoing problem, contact Hivenet Support with the product, device/app or browser version, file count and sizes, start time, progress seen and any error. Tell Support whether it affects one file or several.
For Compute workloads, start with the Compute introduction and documentation so the checks match the resource and task you are running.