Skip to main content

Aztec

Aztec checkpoint production recovers to 100% after a six-hour dip on 20 November

Every Aztec slot has had a checkpoint since 20:25 UTC on 20 November, after ten epochs in which 75 of 320 slots were missed. The cause has not been announced.

Checkpoint production on Aztec's mainnet is back to normal after a dip of about six hours on 20 November 2026. Every slot from epoch 1,560 (from 20:25 UTC) onward has had a checkpoint on Ethereum, and BitBasic's health score for the network is back to Healthy at 100%: 128 of 128 slots in epochs 1,560 to 1,563.

This follows BitBasic's earlier advisory, written while production was still falling.

The dip in numbers

From epoch 1,550 (from 14:01 UTC) to epoch 1,559 (from 19:47 UTC), slots were missed in every epoch. Over those ten epochs, 245 of 320 slots got a checkpoint (76.6%) and 75 did not. The low point was epoch 1,554 (from 16:35), with 17 of 32 slots (53.1%); epoch 1,558 (from 19:08) also fell to 18 of 32 (56.3%) before production recovered.

Proving caught up as well: at 23:02 UTC the latest proven checkpoint was #29,158, with 3 newer checkpoints awaiting proof, against 16 waiting during the dip.

Cause

BitBasic has found no statement from Aztec about the dip, and nothing about it on the Aztec forum, so the cause is still not known.

What it means

  • Sequencer operators: if your node missed duties in these epochs, check its logs from that afternoon. Aztec's docs say a single missed proposal is not slashable, but missing almost all duties over a full epoch can be.
  • Delegators: proposers whose checkpoints did not land earned no rewards for those slots. Your provider's record is on Aztec providers.

Per-epoch figures are on the Aztec epochs list.

Sources