Hacker News Reader

One thing that wasn't clear to me from the documentation: What's the typical latency you observe with this network? Does the routing take physical distance/observed delays into account in some way, or could you wind up with short (in network space) paths that in reality bounce a packet back and forth between the US and New Zealand repeatedly?

View on HN

Latency is dependent on the underlying peering connections. Yggdrasil will try wherever possible to take the shortest paths in network space, but yes, it's possible those could be physically indirect if the underlying peerings are indirect. Generally on the public network (which is probably a couple thousand nodes in number, where people have contributed a number of public nodes and have interconnected them) we see very reasonable latencies.

> Generally on the public network [...] we see very reasonable latencies

Could you elaborate with some specific examples on what you see being "very reasonable latencies"?

I'm getting sub 100ms latencies across the continent with multi hop routes through public peers.

Are you not routing based on latency and reliability like i.e. Babel does? You're only routing based on number of hops?

Reply on news.ycombinator.com