Leaderboard

Reachable Bitcoin nodes ranked according to their Peer Index (PIX) as of Tue Jan 31 08:05:10 2023 EST. PIX values are calculated only for activated IPv4/IPv6 nodes.
JSON API

First / Prev Page 357 of 357 (8908 nodes)

First / Prev Page 357 of 357 (8908 nodes)

Peer Index (PIX)

PIX value is calculated every 24 hours for each activated node based on its properties and network metrics. The value ranges between 0.0 and 10.0 with 10.0 being the most desirable for the Bitcoin network. The formula used to calculate PIX value is described below.

PIX = ((VI + SI + HI + AI + PI + DLI + DUI + WLI + WUI + MLI + MUI + NSI + NI + BI) / 14.0) * 10.0

rs = Rank score
    rs = log(max(1.0, rn))
    rn = normalized reverse rank = ((rv - 1.0) / (rmax - 1.0)) * 10.0
    rv = reverse rank = rmax - (r - rmin)
    r = rank (see details in the particular index below)

cs = Count score
    cs = 1 - (log(c) / log(n))
    n = number of reachable nodes
    c = subset of n (see details in the particular index below)

VI = Protocol version index
    VI = rs
        rs = rank score
        r = rank of node's protocol version
        Most common protocol version is ranked 1 followed by the next most common protocol version

SI = Services index
    SI = √(rs)
        rs = rank score
        r = rank of node's services
        Most common services is ranked 1 followed by the next most common services
        SI is set to 0.0 for node without NODE_NETWORK

HI = Height index
    HI = h / H
        h = node's latest height
        H = consensus height

AI = ASN index
    AI = (cs + (rs * 2.0)) / 3.0
        cs = count score
        rs = rank score
        c = number of nodes from n with the same ASN
        r = CAIDA's AS rank

PI = Port index
    PI = 1.0 for 8333 (default port), 0.0 for other

DLI = Average daily latency index
    DLI = 1.0 for <=  300 ms
          0.9 for <=  400 ms
          0.8 for <=  500 ms
          0.7 for <=  600 ms
          0.6 for <=  700 ms
          0.5 for <=  800 ms
          0.4 for <=  900 ms
          0.3 for <= 1000 ms
          0.2 for <= 1100 ms
          0.1 for <= 1200 ms
          0.0 for  > 1200 ms

DUI = Daily uptime index
    DUI = t / T
        t = number of daily ticks with latency > 0
        T = number of daily ticks
        Tick with latency <= 0 indicates that node is unreachable

WLI = Average weekly latency index
    WLI = 1.0 for <=  300 ms
          0.9 for <=  400 ms
          0.8 for <=  500 ms
          0.7 for <=  600 ms
          0.6 for <=  700 ms
          0.5 for <=  800 ms
          0.4 for <=  900 ms
          0.3 for <= 1000 ms
          0.2 for <= 1100 ms
          0.1 for <= 1200 ms
          0.0 for  > 1200 ms

WUI = Weekly uptime index
    WUI = t / T
        t = number of weekly ticks with latency > 0
        T = number of weekly ticks
        Tick with latency <= 0 indicates that node is unreachable

MLI = Average monthly latency index
    MLI = 1.0 for <=  300 ms
          0.9 for <=  400 ms
          0.8 for <=  500 ms
          0.7 for <=  600 ms
          0.6 for <=  700 ms
          0.5 for <=  800 ms
          0.4 for <=  900 ms
          0.3 for <= 1000 ms
          0.2 for <= 1100 ms
          0.1 for <= 1200 ms
          0.0 for  > 1200 ms

MUI = Monthly uptime index
    MUI = t / T
        t = number of monthly ticks with latency > 0
        T = number of monthly ticks
        Tick with latency <= 0 indicates that node is unreachable

NSI = Network speed index
    NSI = √(log(Pi / 10.0))
        Pi = node's speed percentile (to the nearest percentile between 10th and 99th)

NI = Nodes index
    NI = √(rs)
        rs = rank score
        r = rank of i
        i = p ∩ n
        p = peers returned in addr responses
        n = number of reachable nodes
        Largest i (99th percentile) is ranked 1 followed by the next largest i

BI = Block index
    BI = 1.0 if valid block is returned in response to getdata request, 0.0 if otherwise

Join the Network

Be part of the Bitcoin network by running a Bitcoin full node, e.g. Bitcoin Core.

Use this tool to check if your Bitcoin client is currently accepting incoming connections from other nodes. Port must be between 1024 and 65535.