> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/backup-and-storage/ionos-object-storage/overview/rate-limits.md).

# Rate Limits

IONOS CLOUD Object Storage rate limits protect platform stability against resource-heavy requests and outline how to avoid throttling on IONOS CLOUD

<code class="expression">space.vars.ionos\_cloud\_object\_storage</code> is a shared platform. Rate limits on specific operations prevent heavy usage by one contract from affecting other users. If your requests exceed the limit, the API returns a `429 Too Many Requests` response with a `Retry-After` header.

## Impacted operations

Rate limiting applies to the following operations on Contract-owned buckets:

* **List Objects**
* **Delete Objects**

## Hitting rate limits

Resource-heavy use of the List Objects or Delete Objects operations on [<mark style="color:blue;">Contract-owned buckets</mark>](https://docs.ionos.com/cloud/api-reference/storage-and-backup/ionos-object-storage/ionos-object-storage-for-contract-owned-buckets/) triggers the rate limit, for example through frequent or automated repeated requests against a bucket.

{% hint style="warning" %}
**Important:** <code class="expression">space.vars.ionos\_cloud</code> enforces rate limits per contract, not per user or endpoint. All activity under the same contract counts toward the rate limit.
{% endhint %}

If a request is rate limited, the API returns a `429` response with a `Retry-After` header estimating how long to wait before retrying.

## Mitigation strategies and best practices

If your contract hits the rate limit, consider the following:

1. **Add more time between requests.** This is the primary mitigation: spacing out consecutive List Objects or Delete Objects calls to the same bucket keeps your request rate within the allowed budget.
2. **Avoid unnecessary automated polling.** Review any scripts or integrations that call List Objects or Delete Objects automatically on a fixed, frequent schedule, and increase the interval between calls where possible.
3. **Batch or paginate deliberately.** Where your workflow allows it, retrieve or delete results in fewer, well-spaced calls rather than many rapid successive ones.
4. **Respect the `Retry-After` header.** If you receive a `429` response, wait at least the estimated duration before retrying, rather than retrying immediately.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/backup-and-storage/ionos-object-storage/overview/rate-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.