<p>Peers can get blocked for multiple reasons</p>

<ul>
<li>sending too many invalid blocks</li>
<li>sending too many malformed messages</li>
<li>using too much bandwidth (e.g. your <code>maxuploadtarget</code> setting)</li>
</ul>

<p>and probably others.</p>

<p>There are logs which may be helpful and you can review available options</p>

<blockquote>
<pre><code>-banscore=&lt;n&gt;
Threshold for disconnecting misbehaving peers (default: 100)

-bantime=&lt;n&gt;
Number of seconds to keep misbehaving peers from reconnecting  
(default:86400)


-whitelist=&lt;IP address or network&gt;
Whitelist peers connecting from the given IP address (e.g. 
1.2.3.4) or CIDR notated network (e.g. 1.2.3.0/24). Can be 
specified multiple times. Whitelisted peers cannot be DoS
banned and their transactions are always relayed, even if 
they are already in the mempool, useful e.g. for a gateway
</code></pre>
</blockquote>

CC BY-SA 4.0
2020-04-21T14:38:35.227Z
where can I find my maxuploudtarget?
I just -reindex now to see what will happen
ImCarryGG
CC BY-SA 4.0
2020-04-21T14:22:43.887Z
2020-04-21T14:29:27.783Z
2020-04-21T14:29:27.783Z
RedGrittyBrick
<p>I started downloading the chain and got to 14%. The download stopped and still shows 7% per hour but it does not move.</p>
<p>I checked and it banned all the peers and every time I unban them, they just get banned again. What is happening ?</p>

<bitcoin-core><synchronization><p2p><banscore>
Bitcoin Core banned all peers, so I can't sync
ImCarryGG
# Bitcoin Core banned all peers, so I can't sync

(Asked by: username_0 on 2020-04-21)

I started downloading the chain and got to 14%. The download stopped and still shows 7% per hour but it does not move.

I checked and it banned all the peers and every time I unban them, they just get banned again. What is happening ?

**Tags:** bitcoin-core, synchronization, p2p, banscore


---

## 1 answers

### Answer by username_1 on 2020-04-21. Score: 1

Peers can get blocked for multiple reasons

* sending too many invalid blocks
* sending too many malformed messages
* using too much bandwidth (e.g. your `maxuploadtarget` setting)

and probably others.

There are logs which may be helpful and you can review available options

> ```
> -banscore=<n>
> Threshold for disconnecting misbehaving peers (default: 100)
>
> -bantime=<n>
> Number of seconds to keep misbehaving peers from reconnecting  
> (default:86400)
>
>
> -whitelist=<IP address or network>
> Whitelist peers connecting from the given IP address (e.g. 
> 1.2.3.4) or CIDR notated network (e.g. 1.2.3.0/24). Can be 
> specified multiple times. Whitelisted peers cannot be DoS
> banned and their transactions are always relayed, even if 
> they are already in the mempool, useful e.g. for a gateway
>
> ```

> **Comments:**
> **username_0**: where can I find my maxuploudtarget? I just -reindex now to see what will happen  

---

