Skip to content

Data / Lightning

Lightning Network map

A visualization of the connections in the public Lightning Network.

Loading the map…

Circle size: node capacity

Countries

Share of mapped nodes, and of their capacitynodescapacity

Hosting providers

Share of Lightning capacity by network operator (our node, 27 October 2026)

  1. Amazon.com42.2%313 nodes
  2. Google Cloud19.4%65 nodes
  3. DigitalOcean9.2%112 nodes
  4. DataWeb Global Group B.V.8%5 nodes
  5. UAB Interneto vizija6.9%4 nodes
  6. Hetzner Online GmbH6%151 nodes
  7. OVH SAS4%49 nodes
  8. Alibaba3.9%5 nodes
  9. Zayo3.3%1 nodes
  10. 1984 ehf1.5%15 nodes

Node rankings

Click a column to change the ranking. Figures of 27 October 2026, confirmed when at least 2 up-to-date sources agree within 5% (Amboss, 1ML, LightningNetwork+, mempool.space, and our node). A source whose data is more than 7 days old is shown for reference only.

#NodeCountrySources
1Binance3941542.620233/4 confirmed
2bfx-lnd03375530.612019Switzerland3/4 confirmed
3ACINQ3291,8040.1822018United States3/4 confirmed
4bfx-lnd12645050.5242020Switzerland3/4 confirmed
5fixedfloat.com2391981.22019Lithuania3/4 confirmed
6block-iad-12145140.4162023United States3/4 confirmed
7okx1673860.4322021Hong Kong SAR China3/4 confirmed
8LNBiG [Hub-2]1643160.5212019United States3/4 confirmed
9Strike1353210.422024United States3/4 confirmed
10ed528ad49bedd1f7a638a1342380.5612022United States4/4 confirmed

What the map shows

Each circle is a public Lightning node whose IP address could be geolocated. Its size follows the node’s capacity, the bitcoin locked in its public channels. Lines are the 7,892 largest payment channels between 2 located nodes, except those whose 2 ends sit in the same data center.

Leading country by number of nodes: China, 46.4% of the map, for 0.02% of their capacity. Leading country by capacity: United States, 48.4%.

As of 27 October 2026, Amazon.com alone hosted 42.2% of Lightning capacity, and the 3 largest providers 70.9%. A large part of the network runs in the same few data centers.

On the same date, 4,565 nodes were reachable only through Tor, 32.7% of the 13,970 public nodes counted by our node. They have no location and do not appear on the map.

The Graph tab sets geography aside. These large channels link 1,113 nodes, pulled together by their connections: the nodes at the center are those that hold the most large channels.

What the sources say

No explorer sees “the” Lightning Network: each one sees it from its own nodes and filters it its own way. The gaps mostly come from what each source counts, every announced node or only those it considers active. Our own Lightning node is listed on the same footing as the others: one more observer, not a reference.

SourceNodesChannelsCapacity (BTC)Data as of
mempool.space17,43741,0874,89721 May 2026frozen
1ML5,92119,4612,45627 October 2026up to date
Amboss13,55527 October 2026up to date
Off-Chain Media node13,97034,9353,44627 October 2026up to date

Method and limits

  • The location is that of the server running the node, found from its IP address: a data center, not its owner. A company can run its node in another country.
  • When only the country of an IP address is known, the node sits on a default point for that country. In the United States, that point lies in Kansas, which explains the cluster of large nodes in the middle of the plains.
  • Nodes reachable only through Tor and private (unannounced) channels are invisible here. Channels are drawn only when both ends are located.
  • Capacity shares add up the capacity of every node: a channel counts at both of its ends.
  • The graph only shows the 10,000 largest open channels whose 2 ends are located. Smaller channels and Tor nodes are not in it.
  • Positions, channels and hosting providers: only 2 of our sources publish node locations, mempool.space and our own Lightning node (LND, read by the same open-source software, mempool). Every night, the map takes the more recent of the two readings, and the more complete one when they are from the same day. As of 27 October 2026, that is our node.
  • Key figures and rankings: every night, they are cross-checked across Amboss, 1ML, LightningNetwork+, mempool.space, and our node, with no source given priority. A value is confirmed when at least 2 up-to-date sources agree within 5%; a source whose data is more than 7 days old no longer votes.

Positions and channels: our own LND node, read by the open-source mempool software, which geolocates IP addresses with MaxMind. Basemap: OpenFreeMap, © OpenStreetMap. Map data (JSON)