Solana's First Full Epoch at the 200ms Slot Time Target Averaged 218.3ms and Lasted 26.2 Hours

The first full Solana SOL$110.27+1.8% epoch at the 200ms slot time target has closed, and it averaged 218.3ms per slot. Epoch 1053 began at 14:40 UTC on 9 October 2026 and ended when epoch 1054 began at 16:52 UTC on 10 October, a run of 26.2 hours, according to Solana Compass epoch data pulled at 19:20 UTC on 10 October.

The 218.3ms average is the first measured figure for the 200ms setting, which went live at the epoch 1053 boundary as the last of four reductions under SIMD-0525. Anza, the team that builds the Agave validator client, announced the change at 14:42 UTC on 9 October. A slot is the window in which one validator produces a block. Our figure is an epoch's wall-clock length divided by its 432,000 slots, so the slot average and the epoch length are one measurement stated two ways.

Epoch 1053 ran 18.3ms above the 200ms target, in line with earlier SIMD-0525 steps

Epoch 1053's average sits 18.3ms, or about 9%, above the 200ms target, and each earlier step showed a gap of similar size. The slot-time upgrade page on solana.com dates the 350ms step to epoch 1020, 300ms to epoch 1024, 250ms to epoch 1037 and 200ms to epoch 1053, and marks all four "Live on Mainnet".

In Solana Compass epoch data, slots averaged 365.4ms to 366.8ms across epochs 1020 to 1023, 315.0ms to 317.4ms across epochs 1024 to 1036, and 265.8ms to 268.6ms across epochs 1037 to 1052, the whole of the 250ms stage. Those epochs ran 15ms to 19ms over their targets, and epoch 1053's 18.3ms falls inside that band.

The gap has stayed about the same size in milliseconds while the target has shrunk, so it takes up a larger share of each slot: about 7% in epoch 1052, the last at 250ms, and about 9% in epoch 1053, by the same Solana Compass data. No source we read explains the gap. The solana.com page gives no measured slot times, and an epoch-wide average cannot show where inside an epoch the extra time builds up.

Solana epochs now last 26.2 hours, down from 32.2 hours at 250ms

Epoch 1053 lasted 26.2 hours, against 32.2 hours for epoch 1052, by Solana Compass epoch data. The six-hour cut is what 50ms less per slot comes to over 432,000 slots. Between 20 July and 21 August 2026, when the target was still 400ms, epochs 1005 to 1019 ran 49.9 to 50.8 hours.

Anza's post said an epoch "now takes about a day instead of two", and the solana.com page puts it at "about 24 hours at 200ms". Both are the nominal figure. Measured, the first 200ms epoch ran 2.2 hours past the 24-hour mark. At 26.2 hours, about 335 epochs fit in a year, compared with about 272 at 32.2 hours. Those two counts are our arithmetic, and they assume epoch length holds.

What one 200ms epoch leaves unmeasured: skip rate and the spread of slot times

Epoch 1053 is a single data point. Across the 16 epochs of the 250ms stage, the Solana Compass average moved between 265.8ms and 268.6ms, a range of 2.8ms, so later 200ms epochs may not land on 218.3ms exactly.

An epoch average also hides how individual slots were distributed, and our epoch series carries no skip rate, the share of scheduled blocks that never get produced. The solana.com page says skip rate "was the gating criterion for each step". The only statement we found since activation comes from Anza CEO Brennan Watt, who wrote in a 10 October discussion post that "skip rates look good, and slot times are reasonable", without figures. The post is Watt's proposal to raise Solana's block compute limit.

The second measurement is close. Epoch 1054 was 9.1% complete at 19:20 UTC on 10 October 2026 and, at epoch 1053's pace, would end at about 19:00 UTC on 11 October.