Yggdrasil public peers

github.com · Egress and tunnels · 1 record · JSON

Yggdrasil public peers Egress and tunnels

fails: egressanonymousno cardD

github.com/yggdrasil-network/public-peers · relay network (volunteer) · egress/yggdrasil-public-peers · JSON · compare

Free tier	peering with a volunteer node at the rate it advertises, with no byte meter in the protocol; the overlay carries traffic only to other Yggdrasil nodes unit unlimited; metered on downloaded-bytes
Price	none stated
Per-object cap	not applicable: a routed overlay rather than an object store
Retention	not applicable
Egress	no byte quota exists anywhere in the protocol, and no peer carries traffic to the public internet: the project states it has no exit nodes. The 2.16 TB per day a 200 Mbit/s peer implies is overlay capacity between two Yggdrasil nodes
Identity	anonymous the network is keyed by a self-generated keypair, not an account
Limits	per-ip-shaping whatever the peer grants; the directory lists 100 Mbit/s to 1 Gbit/s per node, which bounds overlay traffic between Yggdrasil nodes source the absence of an exit node is the whole finding and it is not a limit of any of the six kinds: it is a capability the network does not have. Yggdrasil routes inside 0200::/7 only, and the project states that reaching the public internet 'can be achieved using proxies or other tunnelling solutions on top of Yggdrasil but this is not something we explicitly aim to provide'
Binding	none nothing in Yggdrasil binds, because nothing in Yggdrasil carries the client's traffic. The peer's advertised rate bounds overlay volume and is irrelevant to a public serving path
Interface	unknown quic://, tls://, tcp:// or ws:// entries in the Peers[] list of yggdrasil.conf
Tooling	yggdrasil
Composes with	a private mesh between the client's own machines: a node reaches another node's 0200::/7 address with no port forward and no public address. It is not a lane to a reader, so it has no place in a serving chain
Reliability	an alpha-level research project by its own description; the directory is a snapshot of who is currently willing to peer
Notes	Two corrections. And 200 Mbit/s is 2.16 TB, not 2.16 TiB.
Evidence rung	documented the exit-node absence is a first-party statement on the project's own about page, so the field the verdict rests on is documented. Peer rates come from the public directory. No throughput was measured, and none would change the verdict
Checked	2026-10-23 (live); stale on 2026-11-22

Evidence (3)

date	source	what it proved
2026-10-22	yggdrasil-network.github.io/about.html	quoted verbatim: 'Yggdrasil has no native exit nodes, nor does it have any concept of exit nodes, for providing access to the public Internet or to other networks. This can be achieved using proxies or other tunnelling solutions on top of Yggdrasil but this is not something we explicitly aim to provide.'
2026-10-22	yggdrasil-network.github.io/faq.html	quoted: 'Yggdrasil uses the 0200::/7 range, which is a range deprecated by the IETF', and 'While Yggdrasil does transport only IPv6 traffic internally, you do not need an IPv6 internet connection to peer'
2026-10-22	probe:tcp://ygg.mkg20001.io:443	3 of 4 sampled peers accepted a TCP connection from this host: mkg20001, mk16.de and yggdrasil.su open; the Oracle Ashburn address timed out

More fields (3)

{
 "stale_after_days": 180,
 "bytes_transit": "no",
 "transit_note": "Yggdrasil routes only inside its own 0200::/7 overlay and the project states it has no exit nodes, so no peer carries traffic to the public internet"
}

Unknown or withheld values (2)

$.interface interface-unknown
$.notes partly-held

Corrections

2026-10-22 Yggdrasil has no exit nodes, so its 2.16 TB a day reaches no reader
2026-10-22 Yggdrasil example peer is metered