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
ServingGermany
- Observation addresses
- 2 public IPv4
- Map identity
7f2c…91da- Admission
- Externally verified
- Visibility
- Public map
NA-EAST
ServingCanada
- Observation addresses
- 2 public IPv4
- Map identity
c481…2e06- Admission
- Externally verified
- Visibility
- Public map
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.
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