URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
39
Total Peers
26
Online
13
Offline
6131ms
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...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. 23ms -
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. 10ms vpn.helena-cooper.aiclisupervisor
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. 8ms github-watchman, githubproxy, aiclisupervisormanager, cloudrun, buildtest, cockroachdb, lambdastore, hardware-control-fabric, kompile-build-ci, service-atlas, netlab-hosted, productionhealth, simple-filesystem, aforce2-game, simple-filesystem-vnext, containernursery, githubmarkdown, handoff, dockerrun, lambdaserver, performancetest, filedrop, prdashboard, ktestservice, vpn.2f4acf98240f.aiclisupervisor, helloworld, civitdownloader, my-little-agi, digitalocean-droplets, screenshottest, webcron, dockerimages, gitprojecthealth, tasks, namecheap, simpledemo, dependabot, markdown, lossless-cut, snipd-downloader, kompile-remote-build, blobstore, layout, searchable-bucket, streamdemo, daytona-sandboxes
12D3KooW...zaQx
Last seen: just now
198.199.106.165:42509 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. 10ms -
12D3KooW...Zane
Last seen: just now
198.199.106.165:35577 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 -
12D3KooW...GpiT
Last seen: just now
198.199.106.165:37017 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 -
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. 2ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...bavj
Last seen: just now
198.199.106.165:33529 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...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. 2ms vpn.u-corp.aiclisupervisor
12D3KooW...tFBe
Last seen: just now
198.199.106.165:44019 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...KwX2
Last seen: just now
198.199.106.165:34773 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...yqpW
Last seen: just now
198.199.106.165:37877 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...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. 1ms -
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. 4ms -
12D3KooW...9Nze
Last seen: just now
198.199.106.165:42647 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 -
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. 1ms -
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. 3ms vpn.christian-westmont.aiclisupervisor
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. 2ms -
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. 2ms -
12D3KooW...kQHE
Last seen: just now
198.199.106.165:43423 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...m8Rk
Last seen: just now
165.227.24.206:44451 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 -
12D3KooW...3FwX
Last seen: just now
165.227.24.206:34559 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...ZUE8
Last seen: just now
206.189.69.12:39033 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 -
12D3KooW...YwR8
Last seen: just now
206.189.69.12:34397 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...zqcG
Last seen: just now
206.189.69.12:44833 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...NseK
Last seen: just now
206.189.69.12:33805 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...ne4e
Last seen: never
127.0.0.1:44955 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...jxoF
Last seen: never
143.198.236.68:45051 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...w5ij
Last seen: never
143.198.236.68:45717 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...x7tD
Last seen: never
127.0.0.1:44187 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...ykg9
Last seen: never
134.199.235.33:38063 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...TSi8
Last seen: never
134.199.235.33:35631 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...GraJ
Last seen: never
64.23.133.38:44025 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. - retry-test-service
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...7rkG
Last seen: never
64.23.133.38:44613 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. - invalid-port-service
Error: Secure ping failed - peer not reachable or identity mismatch
12D3KooW...MMmF
Last seen: never
127.0.0.1:36077 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
12D3KooW...fsR3
Last seen: never
206.189.69.12:42293 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...5byp
Last seen: never
206.189.69.12:37395 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...Gqae
Last seen: never
104.248.75.129:45535 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...Qix2
Last seen: never
206.189.69.12:41593 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