URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
25
Total Peers
24
Online
1
Offline
389ms
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...rrBf
Last seen: just now
198.199.106.165:33509 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. 82ms -
12D3KooW...awXE
Last seen: just now
165.227.24.206:42329 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. 52ms -
12D3KooW...jhTv
Last seen: just now
198.199.106.165:41431 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...jHM7
Last seen: just now
198.199.106.165:38803 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...J4dg
Last seen: just now
198.199.106.165:44579 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. 55ms -
12D3KooW...UR9U
Last seen: just now
198.199.106.165:46695 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...ssd6
Last seen: just now
64.225.115.174:41225 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. 72ms -
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. 21ms vpn.christian-westmont.aiclisupervisor
12D3KooW...2sfJ
Last seen: just now
172.17.0.1:39863 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 vpn.helena-cooper.aiclisupervisor
12D3KooW...cjXs
Last seen: just now
172.17.0.1:45255 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. 19ms vpn.u-corp.aiclisupervisor
12D3KooW...ciYs
Last seen: just now
198.199.106.165:43043 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. 19ms -
12D3KooW...C4LZ
Last seen: just now
198.199.106.165:43251 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...WFFm
Last seen: just now
198.199.106.165:41869 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...YdfB
Last seen: just now
198.199.106.165:37559 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. 57ms -
12D3KooW...kkzX
Last seen: just now
198.199.106.165:45925 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. 53ms -
12D3KooW...VaFY
Last seen: just now
10.232.248.1:44605 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. 15ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...zbk8
Last seen: just now
198.199.106.165:44099 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...j1sf
Last seen: just now
198.199.106.165:45791 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...S3Hh
Last seen: just now
198.199.106.165:33253 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...dyhX
Last seen: just now
104.248.75.129:36759 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. 59ms -
12D3KooW...D6vK
Last seen: just now
198.199.106.165:46087 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...9ZHA
Last seen: just now
198.199.106.165:39221 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...E59o
Last seen: just now
71.198.229.18:45801 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...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. 7ms github-watchman, githubproxy, aiclisupervisormanager, productionhealth, cockroachdb, kompile-build-ci, lambdastore, aforce2-game, simple-filesystem-vnext, containernursery, githubmarkdown, cloudrun, handoff, dockerrun, lambdaserver, performancetest, netlab-hosted, hardware-control-fabric, service-atlas, filedrop, prdashboard, ktestservice, vpn.2f4acf98240f.aiclisupervisor, helloworld, civitdownloader, my-little-agi, digitalocean-droplets, simple-filesystem, screenshottest, webcron, dockerimages, gitprojecthealth, tasks, namecheap, simpledemo, dependabot, markdown, lossless-cut, snipd-downloader, kompile-remote-build, blobstore, layout, searchable-bucket, streamdemo, daytona-sandboxes, buildtest
12D3KooW...EYUK
Last seen: never
127.0.0.1:50855 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