Calico Rate Limits
Calico publishes NO API rate limits, and the honest zero is the finding. The projectcalico.org/v3 API is served by the OPERATOR'S OWN Kubernetes API server — Calico is not the one answering the request, so there is nobody in Calico's position to impose a limit. Whatever throttling a caller meets is the cluster's own, configured by the cluster's own admins.
Calico Rate Limits is the rate-limit profile for Calico on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and note.
Tagged areas include CNI, Containers, eBPF, Kubernetes, and Network Policy.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.