URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
33
Total Peers
25
Online
8
Offline
5261ms
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...1RNW
Last seen: just now
20.51.199.48:37325 ✔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. 66ms -
●
12D3KooW...Pzc6
Last seen: just now
198.199.106.165:33599 ✔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. 1082ms -
●
12D3KooW...BdGz
Last seen: just now
198.199.106.165:39315 ✔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. 589ms -
●
12D3KooW...ZunZ
Last seen: just now
198.199.106.165:34111 ✔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. 288ms -
●
12D3KooW...BWXe
Last seen: just now
198.199.106.165:35625 ✔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. 182ms -
●
12D3KooW...cbYB
Last seen: just now
127.0.0.1:24747 ✘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. 314ms -
●
12D3KooW...Nvyv
Last seen: just now
172.17.0.1:40155 ✔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 vpn.christian-westmont.aiclisupervisor
●
12D3KooW...mTiG
Last seen: just now
172.17.0.1:42757 ✔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. 20ms vpn.u-corp.aiclisupervisor
●
12D3KooW...9ACW
Last seen: just now
198.199.106.165:45323 ✔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. 20ms -
●
12D3KooW...8Smp
Last seen: just now
198.199.106.165:39969 ✔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...5ks1
Last seen: just now
172.17.0.1:44299 ✔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 vpn.lynn-walton.aiclisupervisor
●
12D3KooW...3uPn
Last seen: just now
198.199.106.165:34951 ✔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...zPGW
Last seen: just now
198.199.106.165:34077 ✔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. 68ms -
●
12D3KooW...Rvrd
Last seen: just now
198.199.106.165:38175 ✔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. 141ms -
●
12D3KooW...G5cU
Last seen: just now
198.199.106.165:40301 ✔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. 393ms -
●
12D3KooW...MUQ7
Last seen: just now
198.199.106.165:40229 ✔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. 29ms -
●
12D3KooW...Da4g
Last seen: just now
198.199.106.165:38227 ✔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...3mQk
Last seen: just now
198.199.106.165:45713 ✔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. 145ms -
●
12D3KooW...pe2i
Last seen: just now
57.151.91.165:42177 ✔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. 188ms -
●
12D3KooW...vA4u
Last seen: just now
198.199.106.165:40629 ✔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. 23ms -
●
12D3KooW...NDwu
Last seen: just now
198.199.106.165:41093 ✔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. 172ms -
●
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. 38ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
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. 24ms containernursery, cloudrun, dockerrun, blobstore, streamdemo, hardware-control-fabric, githubmarkdown, webcron, digitalocean-droplets, kompile-remote-build, vpn.2f4acf98240f.aiclisupervisor, buildtest, grok-image-model, my-little-agi, service-atlas, xai, dummy-text-model, prdashboard, lambdastore, aiclisupervisormanager, netlab-hosted, dummy-image-model, gitprojecthealth, handoff, productionhealth, layout, aforce2-game, daytona-sandboxes, helloworld, simple-filesystem-vnext, ktestservice, lambdaserver, searchable-bucket, github-watchman, cockroachdb, simpledemo, screenshottest, snipd-downloader, performancetest, civitdownloader, lossless-cut, filedrop, namecheap, simple-filesystem, githubproxy, tasks, dependabot, dockerimages, markdown, kompile-build-ci
●
12D3KooW...p1Y6
Last seen: just now
198.199.106.165:45983 ✔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...CSm6
Last seen: just now
172.17.0.1:34203 ✔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 vpn.helena-cooper.aiclisupervisor
●
12D3KooW...28Zc
Last seen: never
198.199.106.165:40777 ✔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...QtCT
Last seen: never
198.199.106.165:40863 ✔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...mdKv
Last seen: never
198.199.106.165:35487 ✔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...XFT1
Last seen: never
198.199.106.165:34839 ✔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...gmPb
Last seen: never
198.199.106.165:38965 ✔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...mnsb
Last seen: never
198.199.106.165:41157 ✔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...XBVH
Last seen: never
20.51.199.48:36989 ✔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...g5YP
Last seen: never
57.151.91.165:35621 ✔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