Bitnodes estimates the relative size of the Bitcoin peer-to-peer network by finding all of its reachable nodes.

Node Status

Node information is updated every 10 minutes. Last updated on Fri Nov 14 06:58:07 2025 EST.
This node was first seen 5 years, 6 months ago.
JSON API

  • 45.76.32.61:8333

    45.76.32.61.vultrusercontent.com

  • Daily / Weekly / Monthly

    RTT

  • UP

    Connected since 3 weeks, 3 days ago

    42.6113 Mbps

    Network speed

  • /Satoshi:28.2.0/

    User agent

    70016

    Protocol version

    NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080)

    Services

    923577 (100.00%)

    Height

  • Amsterdam, Netherlands

    Location

    Europe/Amsterdam

    Timezone

    AS-VULTR (AS20473)

    Network

  • 7-day / 30-day / 90-day

    Addr monitor

    Services at this node is marked as active if its address is gossiped alongside the services by its peers during the respective window. Peers will cease to gossip its address if the node is no longer connected either through inbound or outbound connection. Windows are ordered in descending order.

  • 45.76.32.61 

Alerts

Enter your email address to receive an alert from info@bitnodes.io when this node becomes unreachable. The alert will be triggered only if the node's status remains unchanged for approximately 30 minutes. Please note that each email address can be associated with only one node. Your email address will be kept private and solely used for sending alerts for this node.

History

User agent history for this node from the latest to oldest record.

RECORD DATEUSER AGENT
Fri Oct 17 18:51:02 2025 EDT
3 weeks, 6 days ago		/Satoshi:28.2.0/
Sun Apr 16 04:21:28 2023 EDT
2 years, 6 months ago		/Satoshi:24.0.1/
Tue Sep 6 02:07:19 2022 EDT
3 years, 2 months ago		/Satoshi:23.0.0/
Sat Jun 12 10:02:44 2021 EDT
4 years, 5 months ago		/Satoshi:0.21.1/
Tue Dec 8 02:36:37 2020 EST
4 years, 11 months ago		/Satoshi:0.20.1/
Mon Apr 27 22:30:35 2020 EDT
5 years, 6 months ago		/Satoshi:0.19.1/

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.