# Solana’s Alpenglow Logs 404-Millisecond Median Finality in 24-Hour Sample

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/41854
Published: 2026-10-27T16:14:26.000Z
Updated: 2026-10-27T16:14:26.000Z
Section: Technology

> The sample covered more than 357,000 slots, measuring a public RPC node’s view of block settlement rather than an app’s response time.

Solana’s Alpenglow upgrade produced a 404-millisecond median observed finality in a 24-hour mainnet sample, giving users an early measure of how quickly blocks are treated as settled after the consensus switch.

The sample covered more than 357,000 slots during the 24 hours ending Oct. 23 at 8:30 a.m. ET (12:30 UTC). Median observed finality was 404 milliseconds, with a 579-millisecond 90th percentile and a 765-millisecond 99th percentile.

The measurement started when a public RPC node first reported a slot and ended when it reported a root at or above that slot. Finality is the point at which the network treats a block as settled. The clock captured the node’s receipt and processing of a slot, but not the full path from a wallet submission to an exchange crediting an account, a merchant confirming a payment or an app updating its display.

Votor, Alpenglow’s first phase, took over Solana consensus at slot 459,653,000 on Oct. 21, completing the [mainnet activation](<https://www.tokenpost.com/news/technology/37151>). Votor replaces validator vote transactions recorded onchain with direct votes and certificates. Blocks can become final after one or two voting rounds.

The protocol targets finality near 150 milliseconds. That target is a design goal, while 404 milliseconds was the median captured in this particular sample. The two figures measure different things: the target describes the protocol’s aim, and the sample records observed performance during a defined period.

For services that wait for finality before acting, faster network settlement can allow them to proceed sooner. Each service determines when it updates a screen, credits an account or confirms a payment. The 404-millisecond result does not establish how quickly any particular wallet, exchange or merchant responds.

Solana’s confirmed and finalized labels now refer to the same state. The processed label remains a node’s newest view and can still be rolled back. The upgrade changes how validators agree on blocks; transaction execution, formats, programs and user transaction fees remain unchanged.

Comparisons with the prior system require care. A pre-upgrade median of about seven seconds used whole-second getBlockTime differences, while the post-upgrade sample used millisecond WebSocket observations, so the readings are not a same-method comparison. The separate 12.8-second TowerBFT figure is a reference point. Solana’s slot time also changed from 400 milliseconds to 200 milliseconds in stages completed in October; slot time and finality are distinct measures.

Votor is live. Rotor, the planned phase to replace Solana’s Turbine block-propagation system, has no activation date.



## Links in this article

- [mainnet activation](https://www.tokenpost.com/news/technology/37151)
