> For the complete documentation index, see [llms.txt](https://docs.caraml.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caraml.dev/user-guides/router/delete-a-router/delete-router.md).

# Deleting routers

A router that is not currently deployed or in the process of deployment can be deleted. This action will remove the router from the Turing database and the router and all associated versions can no longer be accessed.

Navigate to the Router Details View of your router.

Click on the More Actions button and select Delete Router.

Only a router that is **not currently deployed or in the process of deployment** (indicated by the absence of `deployed` and `updating` status badges) can be deleted. If you want to delete a router that is currently deployed, undeploy your router first.

![](/files/IUQC8hqD5Fcwgm9f1dqR)

Confirm if you want to delete the router.

![](/files/qPDFvugesDqZFeaAhEau)

Once the router has been successfully deleted, you will be taken to Routers List View and will no longer be able to see the router in the list.

![](/files/tt0UiJmBbwa9XkhRAZH5)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.caraml.dev/user-guides/router/delete-a-router/delete-router.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.