Ciena · Rate Limits

Ciena Rate Limits

Ciena's Blue Planet, MCP, and Emulation Cloud APIs are deployed in carrier networks and developer sandboxes rather than as a public multi-tenant SaaS, so rate limits are governed by deployment sizing rather than a published per-second cap. Practical throughput is bounded by the customer's installation footprint (number of MCP instances, Blue Planet microservice scale, underlying database) and any policy thresholds configured by the operator.

3 Limits Throttle: 429
MEFNetwork ManagementOpticalSDNTelecomTM ForumRate Limiting

Limits

Blue Planet API deployment
varies
see Blue Planet sizing guide; not publicly documented
Limits depend on the deployed Blue Planet microservice topology and the carrier's hardware footprint.
MCP REST / RESTCONF API deployment
varies
see MCP admin guide; not publicly documented
MCP applies session-level concurrency controls; numeric ceilings are deployment-sized.
Emulation Cloud (developer sandbox) developer-account
varies
developer-account fair-use; not publicly documented
Sandbox is for evaluation only; no SLA on rate or availability.

Policies

Backoff Strategy
On 429 / 5xx, retry with exponential backoff and jitter; honor Retry-After when present.
Sizing-Based Throughput
Increase practical throughput by scaling Blue Planet microservices or MCP instances rather than expecting cloud-style elastic limits.
Sandbox Fair Use
Emulation Cloud sandboxes are shared developer environments — avoid load-test patterns that would impact other developers.

Sources