Broadcom · Rate Limits

Broadcom Rate Limits

Broadcom does not publish unified API rate limits across its software portfolio. Most management APIs (vSphere Automation, VMware Cloud Foundation, Aria Operations for Applications) run within the customer's own SDDC or SaaS instance, where capacity is bounded by the deployed infrastructure rather than a vendor-imposed per-second cap. Aria Operations for Applications enforces ingestion and query limits documented per-tenant. Consumers should consult the per-product reference for service-specific limits.

3 Limits Throttle: 429
Cloud InfrastructureVirtualizationObservabilityRate Limiting

Limits

vSphere Automation API vCenter / SDDC instance
varies
bounded by customer-deployed infrastructure
API throughput is bounded by the customer's vCenter / VCF deployment, not a vendor cap.
VMware Cloud Foundation (SDDC Manager) API SDDC Manager instance
varies
bounded by customer-deployed infrastructure
Aria Operations for Applications REST API tenant
varies
see tenant-specific documentation
Tanzu Observability / Wavefront enforces ingestion and query rate limits documented per-tenant.

Policies

Backoff Strategy
Apply exponential backoff with jitter on 429 / 503 responses; honor Retry-After when present.
Customer-Managed Capacity
For self-managed Broadcom products (vSphere, VCF), API capacity scales with the customer's own deployment - sizing the management plane is part of capacity planning.
SaaS Tenant Limits
For SaaS products (Aria Operations for Applications), ingestion and query limits are tenant-specific and documented per service.
Capacity Increase
Higher SaaS-tenant capacity is negotiated through Broadcom support / sales as part of the license agreement.

Sources