This is the name of the release and the specific filename you have chosen to download. An (!) appears if the file is detected as a duplicate of another download which still has a valid token.
This shows the IP address that is allowed to download the file. A tick indicates it is valid. A cross indicates it is invalid. If you need to update the IP lock, you can click the refresh button in the actions section. Note that you can only do this once per download.
This is how long ago the file download token was created. Hover over it to see the time/date. Downloads are valid for 24 hours.
This is how long before the file download token expires. Hover over it to see the time/date. Once expired, the download cannot be started and you will need to generate a new token for that file.
This is how long ago since the file was first downloaded. Hover over it to see the time/date. Once first started, a file token cannot be deleted since it is now used.
This is how many connection attempts have been made to download the file. We limit this to 25 per token to prevent server hammering. Once you hit this number the token will no longer let you download and you will need to make a new token. If you are experiencing a high number or you hit 25, this can be due to having an unstable connection or your download manager is initiating too many connections.
This is how long until the quota used by your download will be returned to you for use by another download. Once available again, it will show as "Returned". Hover over it to see the time/date. Read below to find out how the quota system works.
This is the size of the file and how much quota it will use.
Download - Downloads the file
Delete - Deletes the token. This can only be done if the file has not been downloaded at least once and the token is still valid.
Refresh - This updates the IP lock and extends the expiry to 24 hours. This can only be done once and only if the token is still valid.
Only valid download tokens appear in the main table. Expired downloads will move to the download history page which can be accessed using the button underneath the main table.
BetaArchive's uses a token based download system. A token is a time limited URL specific to you, your account and your IP address for the file you want to download.
A download token is valid for 24 hours from the time it is created. This can be extended once by clicking the refresh button next to the download to grant a further 24 hours from the time it is pressed. You can also do this if your IP address changes to update the IP lock.
To download, simply:
Once a download has been started it is classed as used and counts towards your quota, and therefore can't be deleted. You can either continue the download, or wait for it to expire and its quota will be returned to you.
This can happens if:
This should only happen if your connection drops during the download after the token expires (active connections will continue even if the token expires). We have put in place the ability to extend your download token time once per file for another 24 hours to help overcome this, but it needs to be done before it expires. Unfortunately if you did not extend it before it expires, you'll need a new download token to resume it again.
Each token can be updated once using the refresh button. This will extend the expiry time and also update the IP lock.
If your IP address changes too frequently you may find it difficult to use our download system.
However, you should ensure that your download manager is not trying to establish too many connections. We have a limit of 6 connections per IP, so we recommend a maximum of 4 otherwise you will hit the connection limit and your token will expire. See below for further information on this.
The connection count will increment every time the download URL is accessed and the download is authenticated.
Reasons why the counter increases include:
We allow a maximum of 25 download attempts (connections) per download token to allow for disconnections and so that you can use a download manager.
Once you exceed 25 download attempts, the token will no longer work and you will need to create a new one.
We have this limit in place to prevent "hammering" our servers with connections which can impact performance for everyone else.
We only have a finite amount of bandwidth, and additional bandwidth is expensive, so to keep it free, fair and fast for everyone we need to limit how much you can download so that everyone has a fair chance.
Every user receives 50GB of quota per day, which is reallocated to you on a rolling basis (see below for details on how this works).
Each user gets 50GB/day of quota, which is reallocated to you on a rolling basis. Rolling means that you'll regain quota throughout a 24 hour period.
How much we return to you and when is calculated based on the size of the file and when you start it.
This is calculated as following, 50GB / 24 hours = 1 hour per 2.08GB. So for example:
You can still download files which are larger than your available quota. A 70GB file, for example, will set a quota expiry time of around 35 hours. Once the quota expiry time elapses, the quota that was used will be available for use again. Overall your average usage cannot exceed 50GB/day.
If you download a very large file, you may find that you go a long period of time (more than a day) without quota available to you.
If your quota is over the maximum allowed you won't be able to start a download until some is returned to you.
Quota is only deducted when you start the download for the first time.
No this isn't a bug. We have files larger than 50GB so if we didn't allow this you would never be able to download them. However, you won't be able to start a new download until your quota has some allowance left.
Your download token was not valid. Ensure that it is correct, has not expired, has not exceeded the number of connections (DL count), and the IP lock is valid.
The file you were looking for could not be found. This usually happens if our database has not been updated after a directory or filename change. These changes are automatic within 24 hours, but sometimes we need to make manual corrections. Let us know if you have this issue and we'll investigate. (In future these errors will be automatically reported to us).
There was a server error on our side. These are usually temporary and resolve themselves quickly, but if it continues for more than 30 minutes, drop us a message.
Something went wrong when we tried to connect you to our archive. This is often temporary, but do let us know if you get this error so we can resolve it quickly.
Over recent years, BetaArchive has unfortunately been forced to implement a fair usage policy on the download system.
The reason for this is because a small percentage of BetaArchive users do not play fair when it comes to downloading from the archive. These users are the reason that we first introduced the 50GB/day average download limit, and then later the addition of the fair usage policy.
In order to protect our infrastructure from abuse by a minority of users, which then impacts those who do play fair, we have had to put in place the following policies:
To avoid being hit by our fair usage policy, you should:
Whilst we have rarely needed to take action on any account as a result of this policy, we should mention that any user can have archive access limited or removed without prior warning if the fair usage policy is broken. You may appeal such an action, but it is unlikely that our decision will be reversed if you have ignored warnings.
We have no plans to change the allowed daily quota or our fair usage policy in the near future, but as our infrastructure evolves changes may be possible. Obviously we never want to impose limits on any users, so please don't give us a reason to enforce the guidelines above.
Please remember, BetaArchive is a free service and bandwidth is limited. Play fair so that all users have an equal opportunity to download and enjoy the archive.
You can still get help in the following ways: