URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
33
Total Peers
21
Online
12
Offline
3145ms
Check Duration

Peer Details

Status Peer Address Bootstrap PublicⓘPublic — 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...Zee5
Last seen: just now
64.225.115.174:44507 ✔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. 131ms -
●
12D3KooW...XXKM
Last seen: just now
64.225.115.174:42453 ✔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. 127ms -
●
12D3KooW...6VJY
Last seen: just now
64.225.115.174:40607 ✔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...XRSA
Last seen: just now
198.199.106.165:34523 ✔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. 144ms -
●
12D3KooW...yLbu
Last seen: just now
198.199.106.165:43915 ✔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. 49ms -
●
12D3KooW...pBVF
Last seen: just now
198.199.106.165:36247 ✔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. 40ms -
●
12D3KooW...1iFv
Last seen: just now
198.199.106.165:37737 ✔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...zier
Last seen: just now
198.199.106.165:38797 ✔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...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. 11ms dummy-text-model, service-atlas, netlab-hosted, cloudrun, grok-image-model, buildtest, githubmarkdown, lambdaserver, webcron, digitalocean-droplets, kompile-remote-build, kompile-build-ci, vpn.2f4acf98240f.aiclisupervisor, githubproxy, namecheap, tasks, prdashboard, helloworld, my-little-agi, xai, aiclisupervisormanager, simpledemo, github-watchman, dockerrun, blobstore, streamdemo, webshot, snipd-downloader, cockroachdb, hardware-control-fabric, simple-filesystem, productionhealth, screenshottest, civitdownloader, performancetest, markdown, filedrop, dockerimages, dependabot, lambdastore, lossless-cut, dummy-image-model, gitprojecthealth, handoff, layout, aforce2-game, searchable-bucket, daytona-sandboxes, simple-filesystem-vnext, ktestservice
●
12D3KooW...gN4K
Last seen: just now
198.199.106.165:42281 ✔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 -
●
12D3KooW...okCg
Last seen: just now
198.199.106.165:35551 ✔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...vR4w
Last seen: just now
198.199.106.165:36539 ✔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...xAuJ
Last seen: just now
198.199.106.165:41561 ✔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...y2aZ
Last seen: just now
198.199.106.165:44879 ✔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...nBQY
Last seen: just now
172.17.0.1:39325 ✔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 vpn.helena-cooper.aiclisupervisor
●
12D3KooW...m3B3
Last seen: just now
198.199.106.165:38625 ✔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...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. 4ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
12D3KooW...Sdxu
Last seen: just now
172.17.0.1:46109 ✔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 vpn.lynn-walton.aiclisupervisor
●
12D3KooW...EZHW
Last seen: just now
172.17.0.1:34367 ✔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 vpn.u-corp.aiclisupervisor
●
12D3KooW...iB3H
Last seen: just now
198.199.106.165:38567 ✔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...kTZJ
Last seen: just now
172.17.0.1:45741 ✔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 vpn.christian-westmont.aiclisupervisor
●
12D3KooW...N2Zh
Last seen: never
198.199.106.165:43575 ✔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...zRbU
Last seen: never
127.0.0.1:43511 ✔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...c2w2
Last seen: never
198.199.106.165:41247 ✔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...HiyS
Last seen: never
127.0.0.1:44831 ✘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...6sty
Last seen: never
127.0.0.1:38061 ✘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...M3kC
Last seen: never
127.0.0.1:34079 ✔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...4zFK
Last seen: never
127.0.0.1:40923 ✘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...332K
Last seen: never
64.225.115.174:46333 ✔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...tEgh
Last seen: never
127.0.0.1:37569 ✘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...Xqo9
Last seen: never
64.225.115.174:39717 ✔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...AYvC
Last seen: never
127.0.0.1:45443 ✘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...ZGu2
Last seen: never
127.0.0.1:42687 ✘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