Live network
The relay map, rendered for humans.
See the public relays Atlas can discover, the regions they serve, and the cryptographic identities clients use to authenticate them.
Loading geographic map…
EU-CENTRAL
ServingZurich
- Observation addresses
- 1 public IPv4 + 1 IPv6
- Map identity
hf0k…ZVg=- Admission
- Externally verified
- Visibility
- Public map
NA-EAST
ServingNew York
- Observation addresses
- 1 public IPv4
- Map identity
Yj+Y…EFk=- Admission
- Externally verified
- Visibility
- Public map
NA-WEST
ServingLos Angeles
- Observation addresses
- 1 public IPv4 + 1 IPv6
- Map identity
8eKd…SS8=- Admission
- Externally verified
- Visibility
- Public map
AP-EAST
ServingHong Kong
- Observation addresses
- 1 public IPv4 + 1 IPv6
- Map identity
JjnN…ziI=- Admission
- Externally verified
- Visibility
- Public map
AU-EAST
ServingSydney
- Observation addresses
- 1 public IPv4 + 1 IPv6
- Map identity
9YpO…AzE=- Admission
- Externally verified
- Visibility
- Public map
Relay-to-relay latency
Round-trip time between relays, in milliseconds.
| Zurich | New York | Los Angeles | Hong Kong | Sydney | |
|---|---|---|---|---|---|
| Zurich | same relay | not measured | not measured | not measured | not measured |
| New York | not measured | same relay | not measured | not measured | not measured |
| Los Angeles | not measured | not measured | same relay | not measured | not measured |
| Hong Kong | not measured | not measured | not measured | same relay | not measured |
| Sydney | not measured | not measured | not measured | not measured | same relay |
Federating relays measure each other once a minute; each figure is the lower of the two directions. A dash marks a pair that is not reporting a measurement.
Live inventory, not an SLA.Records on this page are read from the same Ed25519-signed relay map Atlas clients fetch and verify (
/api/v1/relays). Publication means a signed identity that passed outside-in reachability checks; performance for your pair of nodes is still measured end to end, and nothing here is an availability or SLA statement.How to read this page
Availability is published. Performance is still measured from each endpoint.
A relay appearing in the public map means it has a signed identity and has passed external reachability checks. It does not mean it is automatically the fastest choice for every pair of nodes.
A signed inventory establishes trusted membership.
Atlas clients verify the map before considering a relay. Each selected address must then prove possession of the identity named in that map.
Both endpoints measure the candidates they can share.
Observed RTT, loss, and path health—not geographic marketing labels—determine which direct and relay paths are used.
The matrix ranks paths that cross two relays.
When two nodes are homed on different relays, each adds the matrix figure for that relay pair to the two legs it measures itself, so both ends rank the two-relay path on the same scale as a shared relay. How any-to-any reach works
What you will not see here
Private and on-premises nodes stay private.
Organization-only relays can be pinned in customer configuration without being published to nexusatlas.net. They will not appear on this page, even when used alongside the public relay network.
Private deployment options