I issue eth.syncing and get false even when at the same time blocks are imported. Is this correct behaviour?

Using geth version 1.4.6

2 Answers 2


Yes, correct behavior. false means that your Geth is up to date and is not currently syncing. It keeps importing the latest block to remain up to date. Check eth.blockNumber against a block explorer if you want to double-check.

EDIT: web3.eth.isSyncing() will also return false when syncing has not yet started (or is currently not running). If this is the case, you need to check your networking that you are connecting to peers: Why doesn't my Ethereum node have any peers?

  • 6
    The eth.syncing or web3.eth.syncing returns false, while eth.blockNumber returns 0. It doesn't seem correct at all.
    – Raptor
    Dec 27, 2017 at 10:03
  • @Raptor I'm not sure so I suggest asking a separate question.
    – eth
    Dec 30, 2017 at 14:18
  • eth.blockNumber says 0 for me
    – chovy
    Sep 3, 2021 at 1:00
  • @chovy I am editing the questions that you have made comments to. Maybe you are not getting any peers.
    – eth
    Sep 12, 2021 at 4:54

In my case, it seems synchronizing, I have peers connected and the classic INFO messages, but the output of eth.syncing is false and eth.blockNumber says 0. any ideas??

  • Same problem too :( I hope someone helps us. Mar 22, 2018 at 11:30
  • same for me on ubuntu
    – chovy
    Sep 3, 2021 at 1:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.