Keepalive: A heartbeat for the grid

In everyday English, "keepalive" is not really a word at all. You might say someone is "kept alive" by medical equipment, or that a tradition is "kept alive" through practice. The phrase describes the act of sustaining something that might otherwise stop or die. But in energy and utilities, keepalive has become a technical term with a very precise meaning.

On the power grid and in utility control systems, a keepalive is a small data packet sent periodically between networked devices: a supervisory computer and a remote terminal unit, a control center and a substation, a master and a slave device in a SCADA (Supervisory Control and Data Acquisition) system. The keepalive message is often just a single byte or a brief acknowledgment. It serves two critical purposes. First, it confirms that the communication link is still active and that both ends of the connection are responsive. Second, it prevents the link from being terminated by a timeout. Many network protocols will automatically close a connection if no data passes for a set period. The keepalive defeats this by generating minimal traffic at regular intervals, typically every few seconds to a few minutes depending on the protocol and the application.

Why the metaphor stuck: a keepalive is to a data link what a heartbeat is to a living organism. Both are signs that life, or in this case operational continuity, persists. Both occur at a rhythm. Both stop, and the system is in trouble. The term moved into computing and telecommunications broadly, used in web services, database connections, and any system where unplanned disconnection poses a risk. But it is nowhere more critical than in energy management. If a control link to a remote substation or wind farm silently dies due to inactivity, operators may lose visibility and control just when they need it most.

In utilities, keepalive is usually part of a protocol standard. DNP3, IEC 60870-5-104, Modbus, and other industrial control protocols all include keepalive mechanisms. The messages are kept deliberately small to avoid burdening bandwidth, and their timing is tuned to the needs of the network. A slow-changing rural feeder might need a keepalive only every 30 seconds. A fast-acting protection relay might send one every second. In all cases, the goal is the same: continuous certainty that the connection lives.