Pruned Reth snapshot data is ~64 days behind chain tip

[ApeachM]

Summary

The official Base mainnet Reth pruned snapshot at mainnet-reth-pruned-snapshots.base.org contains block data only up to block ~39,578,591, which is approximately 64 days behind the current chain tip (~42,400,000+).

The snapshot files themselves have recent timestamps (Feb 16–18, 2026), indicating the snapshot generation pipeline is still running, but the source node appears to have stalled around mid-December 2025.

Steps to Reproduce

1. Download the latest pruned snapshot:

   wget https://mainnet-reth-pruned-snapshots.base.org/$(curl https://mainnet-reth-pruned-snapshots.base.org/latest)

2. Extract and start Reth
3. Observe pipeline sync starting from checkpoint ~39,578,591 with target ~42,400,000+

Evidence

latest file: base-mainnet-pruned-reth-1771215895.tar.zst (Feb 16, 2026)
checkpoint:  39,578,591 (~Dec 18, 2025)
target:      42,367,169 (current tip)
gap:         ~2,788,578 blocks (~64 days at 2s/block)

Both the current latest and previously downloaded snapshots have nearly identical file sizes (~882.5 GB), confirming they contain the same stale data from the same stalled source node.

Impact

• Pipeline Execution stage alone takes ~6 days to catch up on modest hardware (12 cores, 46GB RAM, NVMe SSD)
• The snapshot is effectively unusable for quick node bootstrapping
• Users expect the pruned snapshot to contain recent data (within a few days of tip)

Related Issues

• [Reth] No P2P peers discovered when using pruned snapshot #959 — No P2P peers discovered when using pruned snapshot
• could not find latest snapshot on base.org #433 — Snapshot was 34 days behind after download

Environment

• Image: ghcr.io/base/node-reth:latest
• Network: Base Mainnet
• Snapshot type: Pruned

[ApeachM]

Update: I can confirm the pruned snapshot has been updated as of 2026-02-21 (base-mainnet-pruned-reth-1771663639.tar.zst). Thank you for the fix!

The snapshot now appears to be only ~3 days behind the chain tip, which is a huge improvement from the ~64 days lag reported in this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.