URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
39
Total Peers
21
Online
18
Offline
703ms
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...P89a
Last seen: just now
198.199.106.165:45313 ✔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. 407ms -
●
12D3KooW...o7EC
Last seen: just now
198.199.106.165:35217 ✔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...LVeT
Last seen: just now
198.199.106.165:37755 ✔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...EApL
Last seen: just now
198.199.106.165:44469 ✔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...qcmD
Last seen: just now
198.199.106.165:45429 ✔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...6T3P
Last seen: just now
198.199.106.165:37785 ✔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...nBQY
Last seen: just now
172.17.0.1:39325 ✔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.helena-cooper.aiclisupervisor
●
12D3KooW...gN4K
Last seen: just now
198.199.106.165:42281 ✔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...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, webshot, 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
●
12D3KooW...EZHW
Last seen: just now
172.17.0.1:34367 ✔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.u-corp.aiclisupervisor
●
12D3KooW...m3B3
Last seen: just now
198.199.106.165:38625 ✔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. 29ms -
●
12D3KooW...okCg
Last seen: just now
198.199.106.165:35551 ✔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...Uep9
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. 5ms -
●
12D3KooW...kTZJ
Last seen: just now
172.17.0.1:45741 ✔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.christian-westmont.aiclisupervisor
●
12D3KooW...6kFZ
Last seen: just now
198.199.106.165:38989 ✔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...SLAe
Last seen: just now
198.199.106.165:36269 ✔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...1iFv
Last seen: just now
198.199.106.165:37737 ✔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...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. 6ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
12D3KooW...SeqN
Last seen: just now
198.199.106.165:33527 ✔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...iB3H
Last seen: just now
198.199.106.165:38567 ✔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...ejMk
Last seen: just now
198.199.106.165:33547 ✔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...HPAE
Last seen: never
127.0.0.1:37555 ✘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...QBX8
Last seen: never
198.199.106.165:41573 ✔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...XgKP
Last seen: never
198.199.106.165:46185 ✔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...7d6K
Last seen: never
198.199.106.165:45153 ✔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...Huf8
Last seen: never
127.0.0.1:42689 ✘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...NqZb
Last seen: never
198.199.106.165:41305 ✔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...BoAd
Last seen: never
127.0.0.1:46111 ✘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...3haM
Last seen: never
127.0.0.1:39749 ✘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...nWcR
Last seen: never
198.199.106.165:45687 ✔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...5J78
Last seen: never
198.199.106.165:35611 ✔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...jwnb
Last seen: never
127.0.0.1:36621 ✘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...azAy
Last seen: never
127.0.0.1:42779 ✘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...J6c7
Last seen: never
198.199.106.165:39631 ✔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...iu2i
Last seen: never
127.0.0.1:36411 ✘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...aryS
Last seen: never
127.0.0.1:35243 ✘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...xMtR
Last seen: never
198.199.106.165:40105 ✔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...UF1z
Last seen: never
198.199.106.165:46333 ✔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...dxpg
Last seen: never
198.199.106.165:46835 ✔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