This document contains current API restrictions and usage quotas on use of Storage Transfer Service. This page is updated when there are changes to these restrictions and usage quotas.
These quotas apply to each Storage Transfer Service project and each user, and are shared across all applications and API versions used by a given developer project.
Concurrent transferOperations limit
The following table describes the limit for concurrent in-progress
transferOperations
:
Maximum in-progress `transferOperations` | Applies to |
---|---|
200 | project |
Read quotas
Storage Transfer Service implements quotas on the following requests for reading data:
transferJobs
— calls toget
andlist
.transferOperations
— calls toget
andlist
.googleServiceAccount
— calls toget
.
The following table describes the quotas we implement on the API requests listed above:
Maximum requests | Duration | Applies to |
---|---|---|
500 | 100 seconds | user |
2500 | 100 seconds | project |
Create quotas
The following table describes quotas for transferJobs
create
requests:
Maximum requests | Duration | Applies to |
---|---|---|
1000 | 1 day | project |
100 | 100 seconds | user |
1000 | 100 seconds | project |
Patch quotas
The following table describes quotas for transferJobs
patch
requests:
Maximum requests | Duration | Applies to |
---|---|---|
100 | 100 seconds | user |
1000 | 100 seconds | project |
Write quotas
Storage Transfer Service implements quotas for the following
transferOperations
requests to write data:
pause
resume
cancel
The following table describes the quotas we implement on the requests listed above:
Maximum requests | Duration | Applies to | |
---|---|---|---|
100 | 100 seconds | user | |
1500 | 100 seconds | project |
Adjusting quotas
For information on adjusting quotas, see Managing your quota.