> 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/e020002.md).

# E020002

**Resource not found**

HTTP status: `404`

Returned by: Dedicated Networks API, `DELETE /networks/{networkId}`, `DELETE /prefixes/{prefixId}`, `GET /ip-addresses/{ipId}`, `GET /networks/{networkId}/ip-addresses`, `GET /networks/{networkId}/operation`, `GET /networks/{networkId}`, `GET /prefixes/{prefixId}/ip-addresses/{ipId}`, `GET /prefixes/{prefixId}/ip-addresses`, `GET /prefixes/{prefixId}/operation`, `GET /prefixes/{prefixId}`.

## What happened

No network, prefix, operation or IP address with this UUID exists on your account.

## Likely causes

* The UUID is wrong or was never created.
* The resource belongs to another account. The API answers `404` in that case too: it never confirms that someone else's resource exists.
* The resource was deleted and its teardown has completed. A deleted network or prefix reads as `404` from then on.
* No operation record exists for the network or prefix yet.
* For an IP address under a prefix: the address does not exist under that prefix, even if it exists elsewhere.

## How to resolve it

* Check the UUID against your own records or the listing of the resource type.
* After a `DELETE`, a `404` on the next `GET` or `DELETE` is the expected confirmation that the teardown completed. No action is needed.
* If you expected the resource to exist, contact i3D.net support with the `traceId`.

## Example response

```json
{
  "title": "Network not found",
  "status": 404,
  "detail": "network 01984f2e-1c3a-7d21-9d10-3542f27adccf does not exist",
  "code": "E020002",
  "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/e020002.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.
