Oracle Cloud Infrastructure · Rate Limits

Oracle Cloud Rate Limits

Oracle Cloud Infrastructure enforces service-specific limits and quotas per tenancy and per region (e.g. number of compute instances, VCNs, autonomous databases). API request throttling is per-service, per-region, and applied at the API endpoint; clients receive HTTP 429 with Retry-After. Many limits are soft and raisable via a service-limit-increase request from the OCI Console.

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

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

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

Tagged areas include Cloud Computing, Rate Limiting, and Oracle.

3 Limits Throttle: 429
Cloud ComputingRate LimitingOracle

Limits

Service-specific quotas tenancy/region/service
varies
see Service Limits, Quotas, and Usage docs
Each OCI service has its own limit set; many are raisable via support request.
API request throttling tenancy/service
requests_per_second
varies per service endpoint
Throttling responses include 429 with Retry-After.
Eventual consistency service
varies
see service docs
Some services (Object Storage list operations, IAM) are eventually consistent and require retry-on-stale.

Policies

Backoff
Use exponential backoff with jitter on 429 / 503; SDKs ship default retry strategies.
Service-limit increase
Request quota increases via the OCI Console (Governance > Limits, Quotas, and Usage) with justification.
Compartment quotas
Use compartment policies to set per-compartment quota policies (separate from tenancy service limits).
Idempotency
Many OCI APIs accept opc-retry-token to make POST/PUT operations idempotent for safe retries.

Sources