URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
18
Total Peers
17
Online
1
Offline
2008ms
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...VaFY
Last seen: just now
10.134.0.2: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. 1ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...wN1S
Last seen: just now
198.199.106.165:41725 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...XbZV
Last seen: just now
198.199.106.165:43063 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...ogzW
Last seen: just now
198.199.106.165:39917 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...7sbE
Last seen: just now
172.17.0.1:41291 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. 2ms vpn.christian-westmont.aiclisupervisor
12D3KooW...137d
Last seen: just now
198.199.106.165:35365 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...TwEZ
Last seen: just now
198.199.106.165:34849 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...f45N
Last seen: just now
198.199.106.165:33413 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...e4Lx
Last seen: just now
198.199.106.165:35273 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...w2Fk
Last seen: just now
198.199.106.165:42657 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...78jj
Last seen: just now
198.199.106.165:33239 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...RTkw
Last seen: just now
198.199.106.165:46747 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...aqMU
Last seen: just now
198.199.106.165:38095 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...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. 2ms cockroachdb, dockerrun, ktestservice, simpledemo, aforce2-game, searchable-bucket, handoff, snipd-downloader, lossless-cut, hardware-control-fabric, githubmarkdown, blobstore, prdashboard, netlab-hosted, cloudrun, simple-filesystem, productionhealth, buildtest, screenshottest, lambdaserver, civitdownloader, webcron, performancetest, digitalocean-droplets, githubproxy, kompile-remote-build, vpn.2f4acf98240f.aiclisupervisor, markdown, kompile-build-ci, namecheap, filedrop, dockerimages, tasks, dependabot, lambdastore, helloworld, my-little-agi, aiclisupervisormanager, github-watchman, gitprojecthealth, layout, streamdemo, daytona-sandboxes
12D3KooW...HjN1
Last seen: just now
198.199.106.165:38331 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...fbA1
Last seen: just now
198.199.106.165:41781 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...AEkx
Last seen: just now
198.199.106.165:36087 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...yMbb
Last seen: never
127.0.0.1:19487 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