URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

Network Status: HEALTHY
33
Total Peers
25
Online
8
Offline
2727ms
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...bMeD
Last seen: just now
206.189.69.12:35753 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. 99ms vpn.lynn-walton.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. 97ms github-watchman, cockroachdb, hardware-control-fabric, service-atlas, netlab-hosted, cloudrun, simple-filesystem, productionhealth, buildtest, githubmarkdown, screenshottest, civitdownloader, lambdaserver, webcron, digitalocean-droplets, kompile-remote-build, performancetest, markdown, githubproxy, vpn.2f4acf98240f.aiclisupervisor, kompile-build-ci, namecheap, filedrop, dockerimages, tasks, dependabot, lambdastore, prdashboard, helloworld, my-little-agi, lossless-cut, aiclisupervisormanager, simpledemo, gitprojecthealth, dockerrun, handoff, blobstore, layout, aforce2-game, streamdemo, searchable-bucket, daytona-sandboxes, simple-filesystem-vnext, snipd-downloader, ktestservice
12D3KooW...cVbg
Last seen: just now
71.198.229.18:44031 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...bdhA
Last seen: just now
198.199.106.165:45175 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...qzNS
Last seen: just now
198.199.106.165:44087 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. 43ms -
12D3KooW...pV3c
Last seen: just now
198.199.106.165:34769 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 -
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. 8ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
12D3KooW...zCCp
Last seen: just now
172.17.0.1:38957 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.u-corp.aiclisupervisor
12D3KooW...HZTN
Last seen: just now
172.17.0.1:39795 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 vpn.christian-westmont.aiclisupervisor
12D3KooW...PkxT
Last seen: just now
198.199.106.165:46617 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 -
12D3KooW...jNcp
Last seen: just now
198.199.106.165:42789 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. 41ms -
12D3KooW...MEH3
Last seen: just now
198.199.106.165:40795 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...Tfk8
Last seen: just now
198.199.106.165:44725 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...7KaA
Last seen: just now
143.244.190.29:41061 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. 36ms -
12D3KooW...aPHN
Last seen: just now
198.199.106.165:35919 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. 60ms -
12D3KooW...vg2g
Last seen: just now
198.199.106.165:34117 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. 50ms -
12D3KooW...H1Zj
Last seen: just now
198.199.106.165:45301 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...WtWA
Last seen: just now
198.199.106.165:35739 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. 26ms -
12D3KooW...xwuN
Last seen: just now
206.189.69.12:33915 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...FgAj
Last seen: just now
198.199.106.165:34129 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. 16ms -
12D3KooW...4dXL
Last seen: just now
71.198.229.18:38979 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...XL2k
Last seen: just now
198.199.106.165:36461 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...ZcnK
Last seen: just now
198.199.106.165:42847 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...D43v
Last seen: just now
71.198.229.18:42327 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. 208ms -
12D3KooW...PJ4m
Last seen: just now
71.198.229.18:37189 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. 224ms -
12D3KooW...CbE3
Last seen: never
164.92.78.111:43361 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...yzQM
Last seen: never
164.92.78.111:35021 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...7rkG
Last seen: never
144.126.215.114:36813 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
144.126.215.114:42277 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...XWUJ
Last seen: never
164.92.78.111:43063 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...7vZL
Last seen: never
198.199.106.165:34571 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...HSWs
Last seen: never
71.198.229.18:43699 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...VGSt
Last seen: never
71.198.229.18:38703 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