URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
43
Total Peers
32
Online
11
Offline
4152ms
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...uHfd
Last seen: just now
198.199.106.165:36835 ✔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. 302ms -
●
12D3KooW...aCpc
Last seen: just now
198.199.106.165:40981 ✔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. 1485ms -
●
12D3KooW...QQVN
Last seen: just now
198.199.106.165:33583 ✔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. 890ms -
●
12D3KooW...2zMe
Last seen: just now
20.55.15.228:44621 ✔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. 109ms -
●
12D3KooW...dctW
Last seen: just now
127.0.0.1:39897 ✔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...uqNQ
Last seen: just now
198.199.106.165:42933 ✔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...jezt
Last seen: just now
198.199.106.165:42823 ✔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...R58v
Last seen: just now
198.199.106.165:34741 ✔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...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. 5ms vpn.christian-westmont.aiclisupervisor
●
12D3KooW...j3Kz
Last seen: just now
198.199.106.165:39017 ✔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...X272
Last seen: just now
206.189.69.12:35479 ✔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.lynn-walton.aiclisupervisor
●
12D3KooW...dpu6
Last seen: just now
172.17.0.1:40059 ✔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.helena-cooper.aiclisupervisor
●
12D3KooW...3bVg
Last seen: just now
206.189.69.12:34737 ✔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...dC7C
Last seen: just now
198.199.106.165:36155 ✔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...k1i7
Last seen: just now
198.199.106.165:34795 ✔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...VC39
Last seen: just now
198.199.106.165:37999 ✔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...AEMC
Last seen: just now
146.190.45.2:33031 ✔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. 13ms -
●
12D3KooW...tDyo
Last seen: just now
198.199.106.165:42233 ✔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...Xejh
Last seen: just now
146.190.45.2:40575 ✔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...gvG8
Last seen: just now
198.199.106.165:37541 ✔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...smBD
Last seen: just now
198.199.106.165:45055 ✔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...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. 5ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
12D3KooW...rvom
Last seen: just now
198.199.106.165:34417 ✔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...tuGS
Last seen: just now
24.144.89.249:38923 ✔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. 256ms containernursery
●
12D3KooW...izFp
Last seen: just now
198.199.106.165:38187 ✔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...kTTu
Last seen: just now
71.198.229.18: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. 20ms -
●
12D3KooW...zqvB
Last seen: just now
127.0.0.1:32941 ✔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. 46ms -
●
12D3KooW...zVkj
Last seen: just now
71.198.229.18:43069 ✔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...JiK9
Last seen: just now
198.199.106.165:39019 ✔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. 139ms -
●
12D3KooW...Behk
Last seen: just now
198.199.106.165:41995 ✔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...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. 7ms vpn.u-corp.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. 2ms dummy-text-model, service-atlas, netlab-hosted, cloudrun, grok-image-model, buildtest, githubmarkdown, lambdaserver, webcron, digitalocean-droplets, kompile-remote-build, kompile-build-ci, vpn.2f4acf98240f.aiclisupervisor, githubproxy, namecheap, tasks, prdashboard, helloworld, my-little-agi, xai, aiclisupervisormanager, simpledemo, github-watchman, dockerrun, blobstore, streamdemo, snipd-downloader, cockroachdb, hardware-control-fabric, simple-filesystem, productionhealth, screenshottest, civitdownloader, performancetest, markdown, filedrop, dockerimages, dependabot, lambdastore, lossless-cut, dummy-image-model, gitprojecthealth, handoff, layout, aforce2-game, searchable-bucket, daytona-sandboxes, simple-filesystem-vnext, ktestservice, containernursery
●
12D3KooW...gCU9
Last seen: never
206.189.69.12:36393 ✔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...hgsY
Last seen: never
127.0.0.1:38131 ✘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...ZARX
Last seen: never
71.198.229.18:40755 ✔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...Y1ug
Last seen: never
24.144.89.249:33905 ✔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...Af2V
Last seen: never
24.144.89.249:37327 ✔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...BZp7
Last seen: never
146.190.45.2:36041 ✔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...m8J5
Last seen: never
24.144.89.249:37035 ✔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...2T5F
Last seen: never
71.198.229.18:34977 ✔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...Fim7
Last seen: never
206.189.69.12:44375 ✔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...UHjQ
Last seen: never
206.189.69.12:33549 ✔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...jeEr
Last seen: never
206.189.69.12:33497 ✔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