URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
23
Total Peers
22
Online
1
Offline
3197ms
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...2wrv
Last seen: just now
104.248.75.129:36289 ✔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...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. 1165ms dependabot, githubproxy, cockroachdb, hardware-control-fabric, digitalocean-droplets, dummy-text-model, ktestservice, layout, dummy-image-model, streamdemo, vpn.2f4acf98240f.aiclisupervisor, simple-filesystem, dockerimages, gitprojecthealth, performancetest, kompile-build-ci, daytona-sandboxes, simpledemo, githubmarkdown, simple-filesystem-vnext, my-little-agi, lossless-cut, filedrop, tasks, github-watchman, markdown, handoff, lambdastore, aforce2-game, netlab-hosted, lambdaserver, blobstore, screenshottest, aiclisupervisormanager, dockerrun, snipd-downloader, civitdownloader, productionhealth, kompile-remote-build, service-atlas, webcron, helloworld, cloudrun, namecheap, prdashboard, grok-image-model, xai, searchable-bucket, buildtest
●
12D3KooW...FrsM
Last seen: just now
198.199.106.165:37041 ✔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. 1101ms -
●
12D3KooW...kptg
Last seen: just now
198.199.106.165:41041 ✔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. 274ms -
●
12D3KooW...AizB
Last seen: just now
198.199.106.165:42451 ✔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. 715ms -
●
12D3KooW...4fHA
Last seen: just now
198.199.106.165:42035 ✔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...FJP1
Last seen: just now
198.199.106.165:37437 ✔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...6p8i
Last seen: just now
172.17.0.1:44345 ✔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...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. 4ms vpn.lynn-walton.aiclisupervisor
●
12D3KooW...Xfu2
Last seen: just now
198.199.106.165:39773 ✔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...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. 30ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
12D3KooW...fv5i
Last seen: just now
198.199.106.165:43543 ✔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. 103ms -
●
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. 11ms vpn.christian-westmont.aiclisupervisor
●
12D3KooW...NTjJ
Last seen: just now
198.199.106.165:41389 ✔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...BMSf
Last seen: just now
172.17.0.1:42791 ✔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.helena-cooper.aiclisupervisor
●
12D3KooW...Q11U
Last seen: just now
198.199.106.165:44767 ✔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. 61ms -
●
12D3KooW...gniy
Last seen: just now
198.199.106.165:45427 ✔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...o8aC
Last seen: just now
198.199.106.165:34421 ✔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...Jg7W
Last seen: just now
127.0.0.1:57255 ✘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. 135ms -
●
12D3KooW...dSsG
Last seen: just now
198.199.106.165:44843 ✔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...rWuS
Last seen: just now
198.199.106.165:41097 ✔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...oJFk
Last seen: just now
198.199.106.165:45095 ✔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...t2CA
Last seen: never
127.0.0.1:38117 ✔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