<p>Looks like you were just unlucky in choosing your peers.</p>

<p>When connecting to a peer your client and the peer exchange a handshake message. Part of this handshake message is the height of the longest chain the peer has locally stored. Your client will then starting to download blocks until it catches up to the top of the longest chain. If the peers you connect to happen to be also catching up with the chain you will only see the length of their chains and will be unaware about the real length of the longest chain in the entire network.</p>

<p>Nothing to worry about, you will eventually have an accurate estimate of the real length: as soon as you connect to a peer with the longest chain, or one of your peers has caught up to the longest chain, your client will update its estimate.</p>

<p>Reconnecting also works as new peers are chosen. When you wrote your question, on October 24th, the longest chain was <a href="http://blockchain.info/block/00000000000002b032243afa2e7befb3504a26e8743a01d6c1a48663dfd686d8" rel="nofollow">204'663 blocks</a> long, so the ~10'000 blocks or so were quite a long way off. Hopefully by now you caught up to the head of the Blockchain.</p>

CC BY-SA 3.0
2013-01-05T14:49:06.120Z
2013-01-05T14:49:06.120Z
cdecker
<p>I.E. 9900 blocks remaining, 9904 blocks remaining and the total percent synced is decreasing. Is this normal behaviour? I'm on a mobile broadband connection but http connections are working just fine. It also says I have 8 active connections which I understand to be the maximum?</p>

<p>Thanks.</p>

CC BY-SA 3.0
2012-10-24T20:27:07.687Z
The number of blocks remaining is only an estimate, based on what other nodes say. There are maximum 8 outgoing connections, so if you can't receive any of your own, 8 is all you'll see, but that's plenty for synchronizing. Just wait somewhat longer.
Pieter Wuille
CC BY-SA 3.0
2012-10-24T20:37:30.530Z
@PieterWuille Thanks. Just in case this helps anyone a quick reboot has remedied the issue and it is no progressing as one would expect.
satoshiisprettycool
CC BY-SA 3.0
2012-10-24T22:36:18.530Z
Note that downloading the blockchain will greatly speed up the syncronisation process: http://bitcoin.stackexchange.com/questions/799/can-i-download-the-whole-block-chain-from-somewhere
Highly Irregular
<blockchain><client><synchronization>
Synchronising official bitcoin wallet for the first time; at 95% started going backwards
satoshiisprettycool
# Synchronising official bitcoin wallet for the first time; at 95% started going backwards

(Asked by: username_0 on 2012-10-24)

I.E. 9900 blocks remaining, 9904 blocks remaining and the total percent synced is decreasing. Is this normal behaviour? I'm on a mobile broadband connection but http connections are working just fine. It also says I have 8 active connections which I understand to be the maximum?

Thanks.

**Tags:** blockchain, client, synchronization

> **Comments:**
> **username_1**: The number of blocks remaining is only an estimate, based on what other nodes say. There are maximum 8 outgoing connections, so if you can't receive any of your own, 8 is all you'll see, but that's plenty for synchronizing. Just wait somewhat longer.  
> **username_0**: @username_1 Thanks. Just in case this helps anyone a quick reboot has remedied the issue and it is no progressing as one would expect.  
> **username_2**: Note that downloading the blockchain will greatly speed up the syncronisation process: http://bitcoin.stackexchange.com/questions/799/can-i-download-the-whole-block-chain-from-somewhere  

---

## 1 answers

### Answer by username_3 on 2013-01-05. Score: 1

Looks like you were just unlucky in choosing your peers.

When connecting to a peer your client and the peer exchange a handshake message. Part of this handshake message is the height of the longest chain the peer has locally stored. Your client will then starting to download blocks until it catches up to the top of the longest chain. If the peers you connect to happen to be also catching up with the chain you will only see the length of their chains and will be unaware about the real length of the longest chain in the entire network.

Nothing to worry about, you will eventually have an accurate estimate of the real length: as soon as you connect to a peer with the longest chain, or one of your peers has caught up to the longest chain, your client will update its estimate.

Reconnecting also works as new peers are chosen. When you wrote your question, on October 24th, the longest chain was [204'663 blocks](http://blockchain.info/block/00000000000002b032243afa2e7befb3504a26e8743a01d6c1a48663dfd686d8) long, so the ~10'000 blocks or so were quite a long way off. Hopefully by now you caught up to the head of the Blockchain.


---

