Public peers in the Yggdrasil network
Go to file
christoofar aaa25d2462
Update (#480)
taking 443 off of cowboy (moving hosts)
2023-08-11 08:24:13 +01:00
africa Clean up African peers (#435) 2022-12-25 16:08:29 +00:00
asia Clean up dead peers 2023-02-14 22:14:34 +00:00
europe Update (#478) 2023-08-05 20:57:38 +00:00
mena Updated Turkey ipv6 peers to dyndns. (#417) 2022-10-20 20:06:13 +01:00
north-america Update (#480) 2023-08-11 08:24:13 +01:00
other Added my node (#469) 2023-06-09 19:21:48 +00:00
south-america Clean up dead nodes 2022-09-05 18:48:07 +01:00 Update 2020-06-13 19:43:41 +01:00

Public Peers

This repository contains peering information for publicly accessible nodes on the Yggdrasil network.

Note that not all peers in this repository are guaranteed to be online - check the Public Peers page instead to find peers that are online now.

In most cases, public peers should be accessible by adding the string provided for each peer to the Peers: [] section of your yggdrasil.conf configuration file.

Example in yggdrasil.conf:


How do I pick peers?

If you are new to the network then take a look at the Public Peers page to find public peers that are online.

Always try to pick peers that are as close to you geographically as possible, as this will keep the latency of the network down.

If you are using a home connection then you should avoid peering with any nodes that are far away, as you may end up carrying traffic for the rest of the network.

For normal usage, you probably only need 2 or 3 peers.

TLS peers

As of Yggdrasil v0.3.11, peering connections over TLS are now possible. This hides the peering connection inside a regular TLS session, which can help in some cases where firewalls or deep packet inspection may identify or block regular Yggdrasil peering traffic.

TLS public peers are identified by the prefix tls:// instead of tcp://.

Note that, due to the additional layer of encryption, performance via TLS peers may be slightly worse than via regular tcp:// peers.