---
title: "Stop a node"
description: "Stop an E1-series node to free its reserved resources, then start it again when you need it."
content_type: "how-to"
product: "node"
platform: "MyAccount"
url: "/myaccount/node/how-to/stop-a-node/"
topic: ["power-and-lifecycle"]
relationships: {"requires":["/myaccount/node/how-to/create-a-node/"]}
---

# Stop a node

**Stop** is a second way to pause an E1-series node, separate from
[Power Off](/myaccount/node/how-to/power-off-and-start-a-node/). It is offered only for E1 and
E1WC nodes; every other series gets the message **Not allowed to stop node.** Use
[Power Off](/myaccount/node/how-to/power-off-and-start-a-node/) instead.

|                                | Power off               | Stop                                  |
| ------------------------------ | ----------------------- | ------------------------------------- |
| The node's resources           | Stay reserved           | Released, then reallocated on restart |
| Starting it again              | Faster                  | Slower                                |
| Compute billing while paused   | Continues               | Pauses                                |
| Storage, volumes, reserved IPs | Keep billing either way | Keep billing either way               |

Open the node's **Actions** menu and click **Stop**. It is available from **Running** or **Powered
off**. The node moves to **Stopped**. While it is stopped, **Start** is the one action it offers.

Stop pauses the node's compute charges, but billing continues for storage and any attached
add-ons, like volumes or reserved IPs.

To bring the node back, open its **Actions** menu and click **Start**. It starts from **Stopped**
for E1-series nodes. Starting it takes a little longer than starting one you only powered off,
since its resources were released rather than reserved. See
[Power off and start a node](/myaccount/node/how-to/power-off-and-start-a-node/).

To stop a node through the API instead of
the portal, see the [node-action operation](/api/myaccount/operations/node-action/) in the API
reference.