F5 Load Balancer · Rate Limits

F5 Load Balancer Rate Limits

The F5 BIG-IP iControl REST, AS3, and Declarative Onboarding APIs are management interfaces exposed by the customer's BIG-IP instance, not a public multi-tenant API. F5 does not publish per-second rate limits for these management endpoints; throughput is constrained by the BIG-IP TMOS control plane capacity of the deployed device/VE. iControl REST itself supports configurable client-side rate-limiting policies for traffic plane data, but these are tools the customer configures, not a vendor-imposed ceiling.

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

It captures 3 rate-limit definitions, measuring varies.

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

Tagged areas include Application Delivery, BIG-IP, Load Balancer, Networking, and Traffic Management.

3 Limits Throttle: 429
Application DeliveryBIG-IPLoad BalancerNetworkingTraffic ManagementRate 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
Customer-deployed; consult the F5 sizing guide for the specific BIG-IP platform.
AS3 declarations device
varies
serialized through BIG-IP control plane; long-running declarations should be polled via task endpoints
Declarative Onboarding declarations device
varies
serialized through BIG-IP control plane; one onboarding operation at a time per device

Policies

Customer-configured rate limiting
BIG-IP itself can apply rate-limit policies to traffic-plane (data path) flows; this is a tool the customer configures, not a vendor cap on the management API.
Async task pattern
AS3 and DO declarations are asynchronous — submit, then poll the returned task URL for status; do not retry the submit while a task is running.
Backoff on 5xx
BIG-IP control plane can return 5xx during heavy config commits; back off with jitter and retry idempotent reads only.
Authentication
Use token auth (POST /mgmt/shared/authn/login) and refresh tokens; basic auth is supported but discouraged for automation.

Sources