MicroVM Lifecycle

Last verified 16 Nov 2026

DigitalOcean MicroVMs are lightweight virtual machines that run a container image in an isolated kernel, pause automatically when idle, and resume on the next request with memory, files, and processes intact.

A DigitalOcean MicroVM moves between running and paused states with your traffic. You choose most of a MicroVM’s settings when you create it, and the platform pauses and resumes it based on activity. This page describes each state and what triggers the transitions between them.

MicroVM States

A MicroVM is in one of the following states:

State Meaning
creating The MicroVM is being provisioned. Its URL is not ready yet.
running The MicroVM is running and serving requests.
pausing The MicroVM is being paused.
paused The MicroVM’s processes are suspended. Its memory, files, and processes are preserved.
resuming The MicroVM is being resumed from a paused state.
terminating The MicroVM is being deleted.
terminated The MicroVM is deleted.
failed The MicroVM could not be created or stopped working. The failure_reason field explains why.
unknown The platform cannot determine the MicroVM’s state.

Auto-Pause and Auto-Resume

A MicroVM pauses automatically when it is not active for its idle timeout. The idle timeout defaults to 5 minutes. The maximum depends on your plan. You set the idle timeout when you create the MicroVM, and you can change it afterward. You cannot turn auto-pause off.

A MicroVM counts as active when it receives requests to its endpoint or sends outbound network traffic. CPU usage or background work with no network traffic does not count as activity.

Work that does not generate network traffic can be paused before it completes. The MicroVM’s memory, files, and processes are preserved, and the work continues when the MicroVM resumes. Set the idle timeout to fit your workload, and save progress for any work that must finish before the idle timeout elapses.

Timers inside the workload stop while the MicroVM is paused.

When auto-resume is on, which is the default, any of the following resumes a paused MicroVM:

  • An HTTP request to one of the MicroVM’s URLs.
  • A command run with doctl compute microvm exec or the API’s exec endpoint.
  • A console session opened in the Control Panel, with doctl compute microvm console, or with the API’s console endpoint.
  • A file upload or download.

Requests, commands, consoles, and file transfers wait until the MicroVM is running. If you turn auto-resume off when you create the MicroVM, it stays paused until you resume it yourself, and requests to a paused MicroVM fail.

You can also pause and resume a MicroVM manually. A paused MicroVM does not expire. It stays paused until you resume or delete it. For instructions, see How to Pause and Resume a MicroVM.

Settings You Can Change After Creation

You can change a MicroVM’s name, tags, idle timeout, project, URLs, and which telemetry Insights stores while the MicroVM is running or paused. For instructions, see How to Update a MicroVM.

All other settings are fixed at creation, including the size, region, image, auto-resume, environment variables, ports, networking, and outbound policy. To use different settings, create a new MicroVM.

A MicroVM cannot use more memory than its size provides, and it does not have swap. When a MicroVM runs out of memory, the guest kernel’s out-of-memory (OOM) killer ends processes.

Billing by State

Compute charges for vCPU and memory accrue per second, only while a MicroVM is running. Storage charges for the MicroVM’s disk accrue whether it is running or paused. A paused MicroVM incurs storage charges only. For rates, see MicroVMs Pricing.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.