Solana says cutting slot time to 200ms before Alpenglow requires caution

Solana says cutting slot time to 200ms before Alpenglow requires caution

N
News Editor
2026-09-28 15:47:03
Solana said it has gradually reduced its target slot time from 400ms to 250ms, with the network’s skipped-slot rate remaining stable during that process. The chain also said the amount of stall time caused by consecutive skipped slots has fallen. At the same time, shorter slot times have pushed voting latency higher, with nodes in Asia and South America seeing the clearest impact. Because of that trade-off, Solana said it still needs to be cautious about lowering slot time further to 200ms before Alpenglow goes live. The update points to progress in reducing block production intervals, but also shows that network performance gains are not evenly distributed across regions. According to the project’s statement, latency effects on validator voting remain a key constraint in any move toward a shorter slot schedule ahead of the Alpenglow rollout.

Solana said it has gradually lowered its target slot time from 400ms to 250ms, while the network’s skipped-slot rate stayed stable during the adjustment. It also said stall time caused by consecutive skipped slots has shortened.

At the same time, Solana said shorter slot times have led to higher voting latency, with nodes in Asia and South America affected most clearly. For that reason, the project said reducing slot time further to 200ms before Alpenglow goes live still requires caution.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
200

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.