Kuma · Rate Limits

Kuma Rate Limits

Kuma's control-plane REST API has no vendor-imposed rate limit — it runs in-cluster (Kubernetes or Universal) and is bound by the operator's own deployment. Kuma does, however, ship a configurable data-plane RateLimit policy (MeshRateLimit / RateLimit) that consumers apply to mesh traffic between services. That is a feature of the mesh, not a quota imposed on the user.

Kuma Rate Limits is the machine-readable rate-limit profile for Kuma on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring varies and requests_per_second.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Rate Limiting, Service Mesh, and Open Source.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingService MeshOpen Source

Limits

Control-plane REST API deployment
varies
no vendor-imposed limit; bound by control-plane resource limits
MeshRateLimit / RateLimit policy (data plane, user-configured) dataplane
requests_per_second
user-defined per policy; default unset

Policies

User-configured data-plane limits
Operators define MeshRateLimit and RateLimit policies on the control plane; Envoy proxies enforce them at the data-plane edge between services and at gateways.
429 response shape
When a configured rate limit fires, Envoy returns HTTP 429 with optional Retry-After; gRPC traffic returns RESOURCE_EXHAUSTED.
Control-plane sizing
Kuma scales horizontally; throughput on the REST API depends on the deployed control-plane replicas and the number of dataplanes connected.
Multi-zone replication
In multi-zone deployments, policy synchronization between Global and Zone control planes uses xDS / KDS; rate of policy churn affects control-plane resource usage but is not numerically capped.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/kuma-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.