<p>I would estimate that there are 30 public servers and 11 validators as I'm typing this answer.</p>

<p>I estimated the number of public servers by connecting to a number of servers and collecting the node keys of every server connected to them. While node keys are free to change, each server has a unique node key while it is connected. This is used to drop duplicate connections. So this should count each public server once.</p>

<p>I estimated the number of validators by collecting the validator public keys of every validation I saw published over a five minute period. I counted the number of unique validation keys.</p>

<p>I can't see any reason these counts could be too high, but they certainly could be missing some.</p>

CC BY-SA 3.0
2013-10-02T23:12:38.120Z
So you connected to server A, which is in turn connected to servers B and C, and it gave you the unique node keys of B and C (as well as its own). How did you do this? Did you use an RPC command? What about server D, which is connected to C, but not to A?
Manish
CC BY-SA 3.0
2013-10-02T23:18:36.540Z
I used the `peers` command. And I connected to almost half the servers in the process. Since most servers try to have at least 10 connections, that should have almost 100% coverage.
David Schwartz
CC BY-SA 3.0
2013-10-03T04:48:07.087Z
A new feature [peer finder](https://github.com/ripple/rippled/tree/develop/src/ripple/peerfinder) is being developed. This will allow every server to maintain a fairly complete map of the network topology (for all non-private servers).
David Schwartz
CC BY-SA 3.0
2013-10-02T22:53:37.857Z
2013-10-02T22:53:37.857Z
David Schwartz
<p>The size of the Bitcoin network is available here:</p>

<p><a href="http://bitcoinstatus.rowit.co.uk/" rel="nofollow">http://bitcoinstatus.rowit.co.uk/</a></p>

<p>As the page says, they do this by listening for Address messages that are broadcast over the network.</p>

<p>Since the Ripple server is now open-source, we can expect a number of individuals and companies to start running their own nodes. Is there a way to estimate the size of the network, either using an RPC command on the server, or by modifying the server code itself to collect some information about the peers?</p>

<p>I would be interested in the following numbers:</p>

<ol>
<li>Number of public servers</li>
<li>Number of validators</li>
</ol>

<p>I imagine the first one could be obtained by querying peers recursively. Unfortunately the RPC interface is only available to 127.0.0.1 by default. As for the second metric, I'm guessing we can get this by looking at the ledger.</p>

<ripple><network>
How big is the Ripple network?
Manish
# How big is the Ripple network?

(Asked by: username_0 on 2013-10-02)

The size of the Bitcoin network is available here:

<http://bitcoinstatus.rowit.co.uk/>

As the page says, they do this by listening for Address messages that are broadcast over the network.

Since the Ripple server is now open-source, we can expect a number of individuals and companies to start running their own nodes. Is there a way to estimate the size of the network, either using an RPC command on the server, or by modifying the server code itself to collect some information about the peers?

I would be interested in the following numbers:

1. Number of public servers
2. Number of validators

I imagine the first one could be obtained by querying peers recursively. Unfortunately the RPC interface is only available to 127.0.0.1 by default. As for the second metric, I'm guessing we can get this by looking at the ledger.

**Tags:** ripple, network


---

## 1 answers

### Answer by username_1 on 2013-10-02. Score: 6

I would estimate that there are 30 public servers and 11 validators as I'm typing this answer.

I estimated the number of public servers by connecting to a number of servers and collecting the node keys of every server connected to them. While node keys are free to change, each server has a unique node key while it is connected. This is used to drop duplicate connections. So this should count each public server once.

I estimated the number of validators by collecting the validator public keys of every validation I saw published over a five minute period. I counted the number of unique validation keys.

I can't see any reason these counts could be too high, but they certainly could be missing some.

> **Comments:**
> **username_0**: So you connected to server A, which is in turn connected to servers B and C, and it gave you the unique node keys of B and C (as well as its own). How did you do this? Did you use an RPC command? What about server D, which is connected to C, but not to A?  
> **username_1**: I used the `peers` command. And I connected to almost half the servers in the process. Since most servers try to have at least 10 connections, that should have almost 100% coverage.  
> **username_1**: A new feature [peer finder](https://github.com/ripple/rippled/tree/develop/src/ripple/peerfinder) is being developed. This will allow every server to maintain a fairly complete map of the network topology (for all non-private servers).  

---

