URL Protocol Network Health

Monitoring the libp2p peer-to-peer network

✔ Network Status: HEALTHY
69
Total Peers
41
Online
28
Offline
5389ms
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...CDLp
Last seen: just now
127.0.0.1:34179 ✔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...aSSE
Last seen: just now
71.198.229.18:41813 ✔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...uE46
Last seen: just now
71.198.229.18:37261 ✔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. 17ms -
●
12D3KooW...Gppu
Last seen: just now
71.198.229.18:40521 ✔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...oSEP
Last seen: just now
127.0.0.1:38685 ✔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...NxGS
Last seen: just now
71.198.229.18:39091 ✔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...yqhV
Last seen: just now
71.198.229.18:45931 ✔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...CMoB
Last seen: just now
127.0.0.1:38517 ✔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...Bins
Last seen: just now
71.198.229.18:46385 ✔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. 18ms -
●
12D3KooW...tvUA
Last seen: just now
71.198.229.18:45363 ✔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...uihi
Last seen: just now
71.198.229.18:46739 ✔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...r1D7
Last seen: just now
127.0.0.1:40727 ✔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...qewf
Last seen: just now
198.199.106.165:33331 ✔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...ndmR
Last seen: just now
127.0.0.1:35559 ✔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...Gqeu
Last seen: just now
71.198.229.18:46371 ✔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...YxGE
Last seen: just now
71.198.229.18:39431 ✔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...tiXF
Last seen: just now
127.0.0.1:45423 ✔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...grg5
Last seen: just now
127.0.0.1:33595 ✔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...MtPz
Last seen: just now
71.198.229.18:40317 ✔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...Vg72
Last seen: just now
127.0.0.1:42819 ✔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...4kmF
Last seen: just now
71.198.229.18:35089 ✔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...8FuC
Last seen: just now
198.199.106.165:41401 ✔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. 162ms -
●
12D3KooW...M1PW
Last seen: just now
198.199.106.165:37941 ✔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. 842ms -
●
12D3KooW...HCxf
Last seen: just now
198.199.106.165:33847 ✔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. 172ms -
●
12D3KooW...5vfG
Last seen: just now
198.199.106.165:35931 ✔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. 488ms -
●
12D3KooW...t8bo
Last seen: just now
127.0.0.1:42667 ✘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. 33ms -
●
12D3KooW...LdUA
Last seen: just now
198.199.106.165:35403 ✔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...Pzk7
Last seen: just now
198.199.106.165:34317 ✔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. 3ms hardware.control.fabric.daemon, hardware.control.fabric.daemon.12D3KooWBzJshJPwQFdE3VqipUmo4sPdwqcxn7Mg8RhTtQfJVaFY
●
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. 16ms -
●
12D3KooW...Ysok
Last seen: just now
172.17.0.1:43963 ✔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.christian-westmont.aiclisupervisor
●
12D3KooW...bhGV
Last seen: just now
198.199.106.165:42655 ✔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. 27ms -
●
12D3KooW...Sdxu
Last seen: just now
172.17.0.1:46109 ✔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.lynn-walton.aiclisupervisor
●
12D3KooW...YEt7
Last seen: just now
198.199.106.165:40067 ✔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...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. 6ms vpn.u-corp.aiclisupervisor
●
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. 3ms vpn.helena-cooper.aiclisupervisor
●
12D3KooW...P8sV
Last seen: just now
198.199.106.165:44141 ✔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...UP2P
Last seen: just now
198.199.106.165:38241 ✔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...hh3m
Last seen: just now
198.199.106.165:35641 ✔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...HNm7
Last seen: just now
198.199.106.165:39049 ✔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...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. 12ms 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...FC95
Last seen: just now
71.198.229.18:40147 ✔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...eJVY
Last seen: just now
71.198.229.18:40759 ✔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...qXY4
Last seen: just now
127.0.0.1:39037 ✔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...n2Cf
Last seen: just now
198.199.106.165:39987 ✔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...4QxZ
Last seen: never
127.0.0.1:32989 ✔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...H6ZJ
Last seen: never
127.0.0.1:39977 ✘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...4Avg
Last seen: never
127.0.0.1:45745 ✘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...RKxi
Last seen: never
127.0.0.1:44791 ✔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...rrqU
Last seen: never
127.0.0.1:40359 ✔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...jyEt
Last seen: never
71.198.229.18:37927 ✔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...JE8b
Last seen: never
127.0.0.1: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. - -
Error: Secure ping failed - peer not reachable or identity mismatch
●
12D3KooW...tbz8
Last seen: never
127.0.0.1:42949 ✔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...eqdZ
Last seen: never
127.0.0.1:44695 ✔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...BYAE
Last seen: never
71.198.229.18:38839 ✔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...7pZ9
Last seen: never
71.198.229.18:43767 ✔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...5VxM
Last seen: never
71.198.229.18:37279 ✔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...itek
Last seen: never
127.0.0.1:43857 ✔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...bbwU
Last seen: never
127.0.0.1:33879 ✔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...n5He
Last seen: never
127.0.0.1:44893 ✔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...aCdu
Last seen: never
71.198.229.18:34543 ✔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...iuCd
Last seen: never
127.0.0.1:44707 ✔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...4DfZ
Last seen: never
71.198.229.18:37539 ✔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...sCiz
Last seen: never
127.0.0.1:40899 ✔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...2SdU
Last seen: never
104.248.75.129:42907 ✔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...CNqq
Last seen: never
104.248.75.129:34239 ✔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...CqPA
Last seen: never
127.0.0.1:36681 ✔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...MUru
Last seen: never
127.0.0.1:44825 ✔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...nL57
Last seen: never
127.0.0.1:53513 ✘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