URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
32
Total Peers
25
Online
7
Offline
945ms
Check Duration

Peer Details

Status Peer Address Bootstrap PublicPublic — whether this node is reachable directly from the internet. A node is Public when it is not behind a firewall or NAT and advertises a routable public address, so a direct peer-to-peer connection to it (without relaying through another node) is likely to succeed. Latency Services
12D3KooW...4sfd
Last seen: just now
198.199.106.165:42599 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 825ms -
12D3KooW...c64a
Last seen: just now
198.199.106.165:44701 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 759ms -
12D3KooW...DbCa
Last seen: just now
127.0.0.1:36715 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 42ms -
12D3KooW...PH3U
Last seen: just now
206.189.69.12:37309 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 27ms -
12D3KooW...LLpu
Last seen: just now
206.189.69.12:32773 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 19ms -
12D3KooW...DvFV
Last seen: just now
198.199.106.165:38435 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 8ms -
12D3KooW...cVbg
Last seen: just now
71.198.229.18:44031 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 31ms -
12D3KooW...68Ui
Last seen: just now
198.199.106.165:34499 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 6ms -
12D3KooW...1HZ3
Last seen: just now
198.199.106.165:39587 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 9ms -
12D3KooW...zCCp
Last seen: just now
172.17.0.1:38957 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 5ms vpn.u-corp.aiclisupervisor
12D3KooW...VaFY
Last seen: just now
10.232.248.1:44605 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 3ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...a9BX
Last seen: just now
198.199.106.165:39231 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 2ms -
12D3KooW...DHbe
Last seen: just now
198.199.106.165:35357 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 62ms -
12D3KooW...DwfD
Last seen: just now
198.199.106.165:43433 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 90ms -
12D3KooW...co2j
Last seen: just now
198.199.106.165:43139 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 2ms -
12D3KooW...Xzci
Last seen: just now
198.199.106.165:36767 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 4ms -
12D3KooW...jGc2
Last seen: just now
198.199.106.165:45811 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 4ms -
12D3KooW...8esZ
Last seen: just now
198.199.106.165:45785 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 18ms -
12D3KooW...jDyw
Last seen: just now
198.199.106.165:37363 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 1ms -
12D3KooW...MJGA
Last seen: just now
198.199.106.165:32973 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 8ms -
12D3KooW...3PNn
Last seen: just now
206.189.69.12:38499 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 28ms -
12D3KooW...HZTN
Last seen: just now
172.17.0.1:39795 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 167ms vpn.christian-westmont.aiclisupervisor
12D3KooW...bMeD
Last seen: just now
172.17.0.1:35753 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 155ms vpn.lynn-walton.aiclisupervisor
12D3KooW...scMT
Last seen: just now
198.199.106.165:35000 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 3ms cockroachdb, hardware-control-fabric, service-atlas, netlab-hosted, cloudrun, simple-filesystem, productionhealth, buildtest, githubmarkdown, screenshottest, civitdownloader, lambdaserver, webcron, digitalocean-droplets, kompile-remote-build, performancetest, markdown, githubproxy, vpn.2f4acf98240f.aiclisupervisor, kompile-build-ci, namecheap, filedrop, dockerimages, tasks, dependabot, lambdastore, prdashboard, helloworld, my-little-agi, lossless-cut, aiclisupervisormanager, simpledemo, github-watchman, gitprojecthealth, dockerrun, handoff, blobstore, layout, aforce2-game, streamdemo, searchable-bucket, daytona-sandboxes, simple-filesystem-vnext, snipd-downloader, ktestservice
12D3KooW...WbDi
Last seen: just now
198.199.106.165:41579 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. 3ms -
12D3KooW...pgMH
Last seen: just now
127.0.0.1:35069 This node is not publicly reachable — it appears to be behind NAT or a firewall (no routable public address), so connecting to it likely requires relaying through another node. - containernursery
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...nifd
Last seen: never
165.227.24.206:40395 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. - -
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...Htgt
Last seen: never
127.0.0.1:45889 This node is not publicly reachable — it appears to be behind NAT or a firewall (no routable public address), so connecting to it likely requires relaying through another node. - -
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...fcde
Last seen: never
198.199.106.165:35351 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. - -
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...wdEW
Last seen: never
198.199.106.165:35025 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. - -
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...n53r
Last seen: never
198.199.106.165:37925 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. - -
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...YVJU
Last seen: never
206.189.69.12:40891 This node is publicly reachable — it advertises a routable public address and is not behind NAT or a firewall, so a direct connection to it is likely to work without going through a relay. - -
Error: Secure ping failed - peer not reachable or identity mismatch