# Mainnet node (0.22.3) stuck at block #1 during initial sync

**URL:** <https://forum.midnight.network/t/mainnet-node-0-22-3-stuck-at-block-1-during-initial-sync/1130>\
**Category:** Technical Questions\
**Created:** [April 5, 2026, 5:19pm UTC](https://forum.midnight.network/t/mainnet-node-0-22-3-stuck-at-block-1-during-initial-sync/1130 "2026-04-05T17:19:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuta](https://avatars.discourse-cdn.com/v4/letter/y/91b2a8/32.png) [@Yuta](https://forum.midnight.network/u/Yuta)\
**Post date:** [April 5, 2026, 5:19pm UTC](https://forum.midnight.network/t/mainnet-node-0-22-3-stuck-at-block-1-during-initial-sync/1130/1 "2026-04-05T17:19:57Z")

</div>

Hi Mainnet node (0.22.3) stuck at block #1 during initial sync. The DBSync NIGHT token UTXO query takes 72+ seconds (1.2M rows in ma\_tx\_out), peers disconnect before completion. Is there a recommended way to bootstrap initial sync, or a node DB snapshot available?

---

<div class="post-metadata">

**Author:** ![bwbush](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@bwbush](https://forum.midnight.network/u/bwbush)\
**Post date:** [April 13, 2026, 8:42pm UTC](https://forum.midnight.network/t/mainnet-node-0-22-3-stuck-at-block-1-during-initial-sync/1130/2 "2026-04-13T20:42:21Z")

</div>

I experienced this problem both on `preprod` and `mainnet`. In both cases `midnight-node` was rejecting the relevant Cardano block because its timestamp fell outside of the required window. It doesn’t seem to arise from a timezone problem, however.

I had to fix it by modifying the `partner-chains` source code that `midnight-node` uses to check the timestamp.