We're are aware of a stall on the Mainnet Stacks Core and the core team is currently looking into the issue.

The incident has been resolved, and block production has resumed. While the network stabilizes, there may be some intermittent hiccups.

The core team is working with the Signers to upgrade and move the chain along. Meanwhile, if you run any Stacks node or Signer: Upgrade your stacks-core to 3.1.0.0.13 when you do your restore
- Check your node's v2/info: curl -s http://cet.stacksnodes.org:20443/v2/info | jq .burn_block_height
- If the burn block height returned is at or near the current bitcoin tip (check mempool.space), your signer is running okay.
- If not, you will need to restore your stacks-node from a snapshot
- If you have one, restore your stacks-node from your own snapshot (as long as it is older than the stall -- 1:30PM Eastern). If not, use the Hiro archive: https://archive.hiro.so/mainnet/stacks-blockchain/mainnet-stacks-blockchain-3.1.0.0.11-20250707.tar.gz
- Upgrade your stacks-core to 3.1.0.0.13 when you do your restore

If you run any Stacks node or Signer: Upgrade your stacks-core to 3.1.0.0.13 when you do your restore
- Check your node's v2/info: curl -s http://cet.stacksnodes.org:20443/v2/info | jq .burn_block_height
- If the burn block height returned is at or near the current bitcoin tip (check mempool.space), your signer is running okay.
- If not, you will need to restore your stacks-node from a snapshot
- If you have one, restore your stacks-node from your own snapshot (as long as it is older than the stall -- 1:30PM Eastern). If not, use the Hiro archive: https://archive.hiro.so/mainnet/stacks-blockchain/mainnet-stacks-blockchain-3.1.0.0.11-20250707.tar.gz
- Upgrade your stacks-core to 3.1.0.0.13 when you do your restore

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.