Instaclustr API Rate Limits
Overview
NetApp Instaclustr throttles API requests to maintain service stability, this applies to most of our API. The rate limit is imposed on each individual account, and may differ for API endpoints, depending on intended usage of the API endpoint.
From February 2025, NetApp Instaclustr will be rolling out a new rate limiting system, to better reflect the intended usage of each API endpoint. This will provide a more stable API service for everyone, and allow us to appropriately scale the capacity of the API service in line with the scale of our customer’s infrastructure.
Rate limits will be applied initially to the Metrics v2 used for Prometheus and will be extended to further endpoints in the future. If request exceeds an API throttling limit, the response returned has code 429 with message Rate Limit Exceeded.
How request rate limiting is applied
Instaclustr API uses sliding window algorithm to rate limit requests. Your current API usage is the number of accepted requests in the last x seconds where x is the size of sliding window.
Current monitoring endpoints
Our metrics update interval is 20s, the same as the rate limit interval.
| Endpoint path | Default Limit (requests) | Default Interval (seconds) | Dynamic Rate Limit | Comment |
| /metrics/v2/query | 2 | 20 | NA | Prometheus: retrieve a node metrics. Rate limit applies per node |
Need to make more requests?
If you have specific use-case requiring higher rate limit than specified above, please contact [email protected] so that we can review, then increase the limit on your accounts.
Exemption From Rate Limits
Console 2
All requests are exempted from rate limit restriction to ensure smooth user experience on Instaclustr Console.
By Instaclustr Support