F5 Networks · Rate Limits

F5 Networks Rate Limits

F5's API portfolio is split between customer-deployed management APIs (BIG-IP iControl REST, AS3, DO, Telemetry, NGINX Plus, NGINX One, NGINX Management Suite, NGINX Ingress Controller, BIG-IQ) and SaaS APIs (F5 Distributed Cloud Console, Essential App Protect). Customer-deployed APIs are bounded by the deployed device/instance capacity, not a vendor-published rate ceiling. F5 Distributed Cloud Console enforces per-tenant API throttling but does not publish numeric per-second limits in the public docs; tenant administrators can configure throttling on data-plane traffic.

F5 Networks Rate Limits is the machine-readable rate-limit profile for F5 Networks on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring varies.

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

Tagged areas include API Gateway, Application Delivery, Automation, Edge Computing, and Kubernetes.

5 Limits Throttle: 429
API GatewayApplication DeliveryAutomationEdge ComputingKubernetesLoad BalancingMulti-CloudNGINXSecurityWAFRate Limiting

Limits

BIG-IP management plane (iControl REST) device
varies
bounded by BIG-IP control-plane capacity (hardware model or VE size); not a published number
AS3 / Declarative Onboarding declarations device
varies
serialized through control plane; submit + poll task pattern
NGINX Plus / NGINX Management Suite API instance
varies
bounded by the deployed NGINX Plus instance; consult sizing guide for the deployed flavor
F5 Distributed Cloud Console API tenant
varies
per-tenant throttling enforced by the SaaS control plane; numbers not published publicly
F5 Essential App Protect API tenant
varies
per-tenant; not publicly published

Policies

Async task pattern
AS3, DO, BIG-IQ, and Distributed Cloud long-running operations return a task URL; poll it for status rather than retrying the submit.
Token authentication
Use token auth on iControl REST (POST /mgmt/shared/authn/login); use API tokens / certificate auth on Distributed Cloud Console; rotate before expiry.
Backoff with jitter
429/5xx responses indicate transient overload — back off exponentially with jitter on idempotent reads.
Customer-configured rate limiting
BIG-IP and Distributed Cloud both expose rate-limit policy as a feature on the data plane; this is a tool the customer configures for their own consumers, not a vendor-imposed ceiling.
Sizing guides
For deployed products (BIG-IP, NGINX Plus, BIG-IQ), throughput is bounded by the licensed form factor — refer to F5 sizing guides for the platform in use.

Sources