# Rate Limiting In order to ensure the quality of service to all VGS customers and help prevent runaway scripts from depleting customer quotas we have rate limiting in our both sandbox and live environment. ## Limits Limits are set depending on the service type (Inbound/Outbound) and the environment type (Sandbox/Live). #### Inbound traffic Inbound traffic is limited by unique IP, per vault (rpm = requests per minute). If the rate limit is X rpm and the number of IPs N, the max rpm would be X\*N for that inbound route (X = 200 rpm for `SANDBOX`, X = 5,000 rpm for `LIVE`, and N = number of IP unique addresses). * Sandbox - 200 rpm * Live - 5,000 rpm #### Outbound traffic Outbound traffic is limited per vault, a rate limit of X rpm is the limit per vault (X = 200 rpm for `SANDBOX`, and X = 5,000 rpm for `LIVE`). * Sandbox - 200 rpm * Live - 5,000 rpm ## Error If you've reached your limit, all following requests will be interrupted with status code `429` and will be reset after a minute. ## Questions If you have any questions, comments or need to increase your limit, please contact us at --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.verygoodsecurity.com/vault/http-proxy/rate-limiting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.