# What happens when an Ethereum validator goes offline? An offline Ethereum validator misses duties and rewards and may receive ordinary penalties. Downtime by itself is not a slashable offense. Slashing concerns specific conflicting signatures. The cost of being offline also depends on whether the network is finalizing normally; extended non-finality activates additional inactivity penalties. Diagnose the outage without hastily starting a second independent signer for the same key. Evidence: [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/); [Home staking Ethereum](https://ethereum.org/en/staking/solo/); [Slashing protection interchange format](https://eips.ethereum.org/EIPS/eip-3076) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-validator-downtime/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Missed duties:** Offline validators cannot perform their assigned duties. ([Home staking Ethereum](https://ethereum.org/en/staking/solo/)) - **Different offense:** Being offline alone is not the same as signing conflicting messages. ([Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/)) - **Network condition:** An inactivity leak changes penalties during extended non-finality. ([Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/)) ## Find which part of the setup stopped working The signing client depends on working consensus and execution infrastructure, synchronization and connectivity. An apparently running process can still be unable to perform useful duties if its node is behind or disconnected. Check client health, synchronization and duty records before making changes. The operational question is whether valid, timely messages reached the network, not only whether the computer had power. Evidence: [Home staking Ethereum](https://ethereum.org/en/staking/solo/); [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) ## A short home outage is not a double vote Suppose a validator misses several duties during a home connection outage. Those omissions can cost rewards and incur applicable inactivity penalties. They do not by themselves constitute two conflicting signed votes. Starting a backup signer while the original may still be signing creates a different risk. Follow the client’s controlled failover process and preserve signing history. Evidence: [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/); [Slashing protection interchange format](https://eips.ethereum.org/EIPS/eip-3076) ## The same duration can have different consequences When the chain continues finalizing, ordinary missed-duty penalties apply. When finality stalls long enough, the inactivity-leak mechanism increases pressure on validators failing the relevant participation requirements. Do not turn a single past outage bill into a universal hourly penalty quote. Effective balance, duty assignment, protocol version and network condition all matter. Evidence: [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) ## Questions ### Will a power cut automatically slash my validator? No. Downtime alone is not slashable. Specific conflicting proposals or attestations are different offenses, although missed duties still have costs. Evidence: [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) ### Can I guarantee an exact loss for one offline hour? Not from duration alone. The validator’s duties, balance and the network’s finality condition affect rewards and penalties. Evidence: [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) ## Claims and scope ### ethereum-validator-downtime-quick-answer An offline Ethereum validator misses duties and rewards and may receive ordinary penalties. Downtime by itself is not a slashable offense. Slashing concerns specific conflicting signatures. The cost of being offline also depends on whether the network is finalizing normally; extended non-finality activates additional inactivity penalties. Diagnose the outage without hastily starting a second independent signer for the same key. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-downtime-fact-missed-duties Missed duties: Offline validators cannot perform their assigned duties. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-downtime-fact-different-offense Different offense: Being offline alone is not the same as signing conflicting messages. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-downtime-fact-network-condition Network condition: An inactivity leak changes penalties during extended non-finality. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Proof-of-stake rewards and penalties](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/) — ethereum.org contributors. Reward components, missed duties and penalty distinctions; values are not quoted as live rates. Locator: Rewards; penalties; inactivity leak; slashing. Retrieved: 2026-10-02T18:55:26.371Z. - [Home staking Ethereum](https://ethereum.org/en/staking/solo/) — ethereum.org contributors. Running and maintaining execution, consensus and validator infrastructure with a qualifying stake. Locator: How it works; responsibilities; requirements. Retrieved: 2026-10-02T18:55:25.708Z. - [Slashing protection interchange format](https://eips.ethereum.org/EIPS/eip-3076) — Ethereum Improvement Proposals. Signing-history transfer between validator clients does not authorize concurrent independent copies. Locator: Interchange format; import and export; safety. Retrieved: 2026-10-02T18:55:26.323Z. - [Ethereum nodes and clients](https://ethereum.org/en/developers/docs/nodes-and-clients/) — ethereum.org contributors. Post-Merge client roles, optional validators and synchronization modes. Locator: Execution and consensus clients; synchronization; node types. Retrieved: 2026-10-02T18:55:26.405Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “What happens when an Ethereum validator goes offline?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-validator-downtime/