URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
40
Total Peers
33
Online
7
Offline
2837ms
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...zfwc
Last seen: just now
198.199.106.165:37239 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. 389ms -
12D3KooW...s8uA
Last seen: just now
198.199.106.165:45009 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. 362ms -
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. 87ms -
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. 80ms vpn.u-corp.aiclisupervisor
12D3KooW...By9L
Last seen: just now
172.17.0.1:40851 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. 70ms vpn.helena-cooper.aiclisupervisor
12D3KooW...5d9p
Last seen: just now
198.199.106.165:42859 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. 30ms -
12D3KooW...uwuG
Last seen: just now
198.199.106.165:34083 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. 21ms -
12D3KooW...pdG4
Last seen: just now
198.199.106.165:41661 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. 10ms -
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. 12ms 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. 9ms vpn.lynn-walton.aiclisupervisor
12D3KooW...wpgF
Last seen: just now
198.199.106.165:45167 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. 7ms -
12D3KooW...E6LZ
Last seen: just now
198.199.106.165:35657 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...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. 2ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...KVZk
Last seen: just now
198.199.106.165:33769 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...oGcF
Last seen: just now
198.199.106.165:43437 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. 37ms -
12D3KooW...sXQr
Last seen: just now
71.198.229.18:45123 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. 25ms -
12D3KooW...2atp
Last seen: just now
146.190.34.207:41703 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. 11ms -
12D3KooW...1BXZ
Last seen: just now
198.199.106.165:37287 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...CxXX
Last seen: just now
198.199.106.165:39665 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. 12ms -
12D3KooW...mwnx
Last seen: just now
71.198.229.18:46253 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. 16ms -
12D3KooW...obeR
Last seen: just now
71.198.229.18:33593 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. 17ms -
12D3KooW...SFYo
Last seen: just now
71.198.229.18:45031 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. 22ms -
12D3KooW...XgCM
Last seen: just now
198.199.106.165:35497 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. 13ms -
12D3KooW...2sce
Last seen: just now
71.198.229.18:35913 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...MKhc
Last seen: just now
71.198.229.18:36187 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. 33ms -
12D3KooW...fWHs
Last seen: just now
64.225.115.174:41055 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. 15ms -
12D3KooW...yrki
Last seen: just now
198.199.106.165:41241 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. 24ms -
12D3KooW...8Mdz
Last seen: just now
198.199.106.165:35737 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. 11ms -
12D3KooW...c2hU
Last seen: just now
64.225.115.174:46343 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. 14ms -
12D3KooW...QiWw
Last seen: just now
198.199.106.165:42411 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 -
12D3KooW...JiXt
Last seen: just now
64.225.115.174:36019 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. 10ms -
12D3KooW...zCvT
Last seen: just now
198.199.106.165:38157 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. 7ms -
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. 16ms 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...ZqsM
Last seen: never
127.0.0.1:38359 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...hc7K
Last seen: never
64.23.179.105:39961 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...iaJf
Last seen: never
137.184.124.90:44335 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...bk7x
Last seen: never
64.23.227.78:41705 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...1AcF
Last seen: never
198.199.106.165:42781 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...QUpK
Last seen: never
198.199.106.165:37669 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...kRLV
Last seen: never
64.225.115.174:45831 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