> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/api/errors/e020016.md).

# E020016

**Quota exceeded**

HTTP status: `409`

Returned by: Dedicated Networks API, `PUT /networks/{networkId}`, `PUT /prefixes/{prefixId}`.

## What happened

The create would take your account past one of its limits. Nothing was created and no operation was started.

## Likely causes

* You hold as many networks in the fabric as your limit allows.
* You hold as many prefixes in the network, or across your account, as your limit allows. On a network create, the initial prefixes count too.

## How to resolve it

* Read `detail`: it states the limit, your current usage and how to request a raise.
* Release a resource you no longer need, then send the same request again.
* Or contact i3D.net support to request a higher limit. `GET /usage` shows your limits and headroom; see [Usage and limits](https://docs.i3d.net/connectivity/dedicated-networks-api/usage-and-limits.md).

## Not to be confused with

`E020017` (missing contract) means your account has no contract for creating resources. If you get `E020016`, you have a contract but you hold as many resources as the maximum it allows.

## Example response

```json
{
  "title": "Quota exceeded",
  "status": 409,
  "detail": "your limit of 5 networks in fabric 'montreal-a' has been reached (5 in use); release one you no longer need, or contact i3D.net support to request a higher limit",
  "code": "E020016",
  "traceId": "0af7651916cd43dd8448eb211c80319c"
}
```


---

# 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.i3d.net/api/errors/e020016.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.
