ln.watch

Public watchtower directory

No signup · no API key · static

99 towers listed · 85 probed hourly · 1 responding · 14 speak another protocol · swept 6 min ago

Every row carries the URL where its address was published. A tower whose provenance we cannot show is not listed. The finding is the shorter version of this table.

What a probe proves

The tower answered on its published address, completed the handshake against its published key, negotiated a session for a real channel type, and acknowledged an encrypted update we uploaded. We then deleted the session. Measured hourly from a Lightning node we run, and published here.

What no probe proves

That the tower would broadcast a justice transaction if your counterparty published revoked state. That takes a real breach, on mainnet, with a real channel. Nobody publishes that data. Neither do we. Anyone claiming to verify watchtower efficacy without paying for breaches is guessing.

What “accepted” and “acknowledged” mean

The watchtower protocol has eight messages and none of them returns a stored blob — a tower only ever hands the data back to the chain, on a breach. So no client can read its own backup back, and neither can we. Stored is the tower’s claim; acknowledged is ours. We upload an update rather than stopping at the session because a tower whose disk is full will negotiate a session quite happily and then fail to store — that failure is visible and we report it. A tower that acknowledges an update and then loses it is not distinguishable from one that keeps it, by us or by anybody.

Show
Historyone cell per day, newest rightSourcewhere it was published
kieselbert
03904f1a0e…60a173
91.99.137.37:9911
185.156.174.27:9912
responding356 / 356
100.0 %
117 ms
clearnet
legacyanchortaproot32 min14 d
15 days watched
postnasal
03ed5ada06…c91221
yps6664vz36t….onion:9911
intermittent
timed out
352 / 356
98.9 %
519 ms
via tor
legacyanchortaproot29 min14 d
15 days watched · 3 slow
pcwd
0240b55b06…2165fb
ken624w6pe4c….onion:9911
4csapo3xof4u….onion:9911
110.32.31.91:9911
+4 more published, none answering
intermittent
timed out
349 / 356
98.0 %
1 115 ms
via tor
legacyanchortaproot30 min14 d
15 days watched · 4 slow
alexpr111
032c0267b5…dcc730
6xrdasyxbpvl….onion:9911
intermittent
timed out
342 / 356
96.1 %
841 ms
via tor
legacyanchortaproot35 min14 d
15 days watched · 2 slow
w1ll
03d4936be4…99d53e
tbkzib3qfhwk….onion:9911
intermittent
timed out
340 / 356
95.5 %
674 ms
via tor
legacyanchortaproot28 min14 d
15 days watched · 2 slow
tylonhh
031e4e8aa2…aedb36
stzt3xmwtqce….onion:9911
intermittent
timed out
338 / 356
94.9 %
534 ms
via tor
legacyanchortaproot29 min14 d
15 days watched · 2 slow
bulltower
021cf04324…a86446
a6z5w3wiymr4….onion:9911
intermittent
timed out
286 / 356
80.3 %
546 ms
via tor
legacyanchortaproot34 min14 d
15 days watched · 1 failed · 1 slow
136.53.106.61
02c4d34258…58438c
136.53.106.61:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
157.245.68.69
038f7f3668…aef425
157.245.68.69:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
65.21.175.152
0202e7727e…55a0df
65.21.175.152:9911 wrong key
not responding
stale listing — the host answers, the published key does not
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
7ykwxs6l
020ecd2e0e…62f434
7ykwxs6ln3o4….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
behodl
0246cc7305…93218c
7onkhjszsznx….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
benthecarman
02af24d729…5ce450
6kvvj7srf2lr….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
bitcoingamer21
02b759a578…0685c1
116.202.17.127:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
candlehater
03c4a044aa…56356e
3y7d6dpkztdm….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
capitanman
02dcdcb4e7…497c41
42ufqkrh6ttk….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
cercatrova21
02091694e1…519e7e
w4p4icmtov7s….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
cryptogamer21
02e87f4842…cb28f8
ccbjcdu7x74v….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
curemici
0286ff6b71…735852
kmtmyodzpq7k….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
davidhrinaldo
02ba974c04…c444df
147.182.218.169:9111
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
ddoi7crm
02f1158dd6…050bc1
ddoi7crm7rhj….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
dragsugg
02383d3698…f28243
ktddfyvrnz4m….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
dvarao
0231288e5b…ea393d
caes52jnrt5p….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
enorrmann
0245d6e965…d421a2
rayo.host:9911
not responding
host does not resolve
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
faket0shi
03f86629f1…2edb18
64r2atc4druu….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
fbrz76-frznode-2
028829fcc0…ce44ea
6kh3htmifene….onion:9911
zt-us.frznode.com:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
frznode
03b06847b0…5b1b0d
ulth7cn7un7w….onion:9911
154.26.156.214:9999
wt2.frznode.com:9911
zt-au.frznode.com:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
frznode-2
032b32484f…8f79ab
gjlimbqvzyuh….onion:9911
wt1.frznode.com:9911
5632omxc6qlr….onion:9911
zt-eu.frznode.com:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
fxprofitsync
0238b13c98…c56d0d
awunivieaeqm….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
githubuser175
03d475b252…8a92fd
dx7b5wqgbnlc….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
grnqrtr
03f00990e6…2760c6
er5zkw5hn4oh….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
h2ogeek
02855af21a…1bae4b
4a6brdux7pel….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
homecrypt
03ab82d182…68b4a8
ln.homecrypt.net:9911
173.50.76.53:9911
not responding
host does not resolve
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
janstr95
0274a6c5e9…fbe9e6
jtnyj5eqenu4….onion:9911
qvumwruxhk5s….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
javilib
0354d80bcc…4bd9c9
94.177.171.73:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
javilib-2
035ec8052d…470d1b
51.255.211.238:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
jo6psaa3
03bb5606c4…3a8e38
jo6psaa3krmb….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
johnongit
0307da8721…f98cef
141.145.193.235:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
johnongit-2
0368d7d26b…dfe782
w6fsnxcemcyb….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
jomaanro
028af801e7…7c360a
141.138.142.171:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
juized
022651061a…47e2ab
y4zxfirsbdjq….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder
0201fb7bc8…29b153
177.204.239.6:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
lightninghoarder-2
034fec0f75…3490c5
ypnweghgxkoo….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-3
02594d02da…7cba0a
rpl4c5zvrtkc….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-4
03a5fbe039…a3c6d8
nwehukwznota….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-5
023624ec8f…bcffcc
vjmidirprcpn….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-6
03ac8be74d…7093b3
lxg2l6ymquk6….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-7
029643a18e…010e81
luhnowuxywvg….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lightninghoarder-8
03bdee2e3c…ff2c14
wasmzkmeb53r….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
ln-voltage
023bad37e5…2b60bf
iiu4epqzm6cy….onion:9911
34.216.52.158:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lnrouting
03644c350c…758d28
aroxsistvam7….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
lowryn
0307df9b5c…39f2b8
x2aw5ca4qg2c….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
marcoblue
0363d5a612…51894a
rxhbmcpmudyo….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
massimoscacchi
032476865d…ab9b94
ubeaan3f2c3o….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
mattes075
025152a29d…25626a
tz6n737lcizn….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
megalith
02169b6d1d…e639a0
3jkueebmhtge….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
microbolt
02929aec32…68a928
ypeqsjqgafod….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
minervaaaaa
022ad5e6f5…6aa65f
vnbymdtj5odc….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
mistersplice
020d679437…0edbee
h7xeed4ta3mg….onion:9735
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
ngutech21
03acd431db…ca237e
xkjsjmxbalim….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
nicolasb58
0306fe3df7…9ee1d7
uspe7xbwh2nz….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
nolim1t
02c690cdb8…77f689
lncmnlgypuendl5t.onion:9911
ln-vps.nolim1t.co:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
openoms
02b745aa2c…39ea82
67dhenmvdyyl….onion:9911
xjyldrwmtxtu….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
ovrhgl47
039ce85b14…56c063
ovrhgl47prkm….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
patrikmojzis
02ac9285de…8022e1
wf5vd2z2vlrk….onion:9911
84.238.56.45:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
pipor
027baa1cc7…69f9d8
o6cqgkwmhrn6….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
plebnet
02c6d32c05…2e5d96
uoyands3phvs….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
plebnet-2
031557cea4…1f67fb
3zlvbas7neqm….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
posted
03fdd72f08…0e8324
mcnfok66tvfl….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
ppachur
02d651a0e8…1150f7
212.86.32.106:9911
not responding
network unreachable
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
primexz
02e5eb5b62…8b7681
167.235.144.119:9911
ydmdmjfjtmyf….onion:9911
not responding
timed out
0 / 356
0.0 %
clearnet
14 d
15 days watched · 15 failed
proof
023c2f2f28…cbcc70
duhm2urtjlpx….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
romanneuromancer
02e2e7a151…3efc86
hikn222xb6ig….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
roshan
0388a793b8…490d2c
7lmah4gnwo4k….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
rstoffel
03f5409765…8d2c95
twlbwoqb3lhm….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
singlebeam
02ad47b4e4…a2726b
zm32w2qs2lf6….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
songo9342
037b41f25c…2fca8c
wxlxqbdxky75….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
stacki89
02ca3aadef…b8e371
ullc7amq6alg….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
urentropy
03e15761d0…580142
yif2w3dmxuis….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
vitminee
037f711de3…1a4b13
5p76dgw5ggea….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
volatility4sale
0395c87a9d…eacd05
rvzvckh34hmh….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
voltage.cloud-ln
0301135932…e6a3d6
tower4excc3j….onion:9911
44.237.235.163:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
we
02093be376…e579b7
yz5xfhhkyu2n….onion:9911
not responding
timed out
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
weebdatahoarder
025d21fc58…0279db
looplnk2vszf….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
yourdevice.ch
0214365a2c…6d1033
yreb4gbnfi5e….onion:9911
not responding
tor could not build a circuit
0 / 356
0.0 %
via tor
14 d
15 days watched · 15 failed
3cola
03cb971ac0…6e3532
tmt7k3fta6w6….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
capitan
022233128e…2b2b26
ykquhk73nhcj….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
cmdrzod
021366c98e…827baa
7lqfpop2kbfp….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
decentralizedb
03488e12bc…5175cc
nbwvzyiicsg7….onion:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
fbrz76-frznode
032a4ff7dd…11339a
devrzfhfi2xa….onion:9814
wt2.frznode.com:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
jochemin
028b85eb14…799eb4
zn55t2ihb5pe….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
lunaticoin
029ba52e77…f0b1af
ygrb66xi53wj….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
mariocynicys
031421fe4a…6ffe40
kfve5m2gzkre….onion:9814
teos.mariocynicys.me:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
orbitalturtle
03d8e71945…b2d180
dbed7lompa5u….onion:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
sat
03b0a47228…75a1dd
satseye.slicksparks.ky:9814
ekeyon2bbc3b….onion:2121
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
clearnet
not probed by us
sr
02b4891f56…d24436
recnedb7xfhz….onion:9814
teos.talaia.watch:9814
mainnet.eyeofsatoshi.watch:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
via tor
not probed by us
ulrichard
0212461401…dbb4f4
ulrichard.ch:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
clearnet
not probed by us
ulrichard-2
027f4e064c…b70723
65.109.24.172:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
clearnet
not probed by us
ulrichard-3
03408b5923…a33b1e
65.108.101.79:9814
no data
not probed by us — teos does not speak lnd's watchtower wire protocol; this prober does not probe it
clearnet
not probed by us
not responding — no attempt negotiated a session no data — no completed attempt intermittent — some attempts did responding — every attempt did

The legend is in rank order — act, unknown, watch, nominal. A blind spot outranks a measured deviation, which is why no data sits above intermittent and is never rendered as a failure. The table itself is sorted working-first for the reason below.

Default order is working first. Everywhere else in this product a list of states is ranked worst-first, because a health screen answers “what needs me”. This table answers “which tower should I use”, and putting 84 dead towers above the 1 live ones would bury the only rows anyone can act on. Sort any column to override it.

A tower published at more than one address is one row, not two — a tower is its key. Its figures are those of its best-performing address, and the addresses it does not answer on are listed beneath it. An address that answers on TCP while the key published for it does not is a stale listing rather than an outage, and is marked as such.