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.

Connecting to the live feed…—
Public relays—Published identities
Serving regions——
Map formatv—Ed25519 signed
Data sourceConnecting…/api/v1/relays · signed inventory
Live relay inventoryFetching the signed map Atlas clients verify…
Loading geographic map…
Relays
5Published identities
Regions
5Serving
Measured
0 of 10Relay pairs
Median
—No pair reporting
Lowest
—No pair reporting
Highest
—No pair reporting
Map format
v1Ed25519 signed
Public relay, one marker per regionNatural Earth basemap, served from nexusatlas.netFull relay-to-relay matrix

Relays by region

5 relays · west to east
NA-WEST

Los Angeles

Serving
Observation addresses
1 public IPv4 + 1 IPv6
Map identity
8eKd…SS8=
Admission
Externally verified
Visibility
Public map
NA-EAST

New York

Serving
Observation addresses
1 public IPv4
Map identity
Yj+Y…EFk=
Admission
Externally verified
Visibility
Public map
EU-CENTRAL

Zurich

Serving
Observation addresses
1 public IPv4 + 1 IPv6
Map identity
hf0k…ZVg=
Admission
Externally verified
Visibility
Public map
AP-EAST

Hong Kong

Serving
Observation addresses
1 public IPv4 + 1 IPv6
Map identity
JjnN…ziI=
Admission
Externally verified
Visibility
Public map
AU-EAST

Sydney

Serving
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.

0 of 10 pairs measured
Relay-to-relay round-trip time in milliseconds
Los AngelesNew YorkZurichHong KongSydney
Los Angelessame relaynot measurednot measurednot measurednot measured
New Yorknot measuredsame relaynot measurednot measurednot measured
Zurichnot measurednot measuredsame relaynot measurednot measured
Hong Kongnot measurednot measurednot measuredsame relaynot measured
Sydneynot measurednot measurednot measurednot measuredsame 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.

01 · Publication

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.

02 · Selection

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.

03 · Relay to relay

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

04 · Modes

The same relays carry every mode.

A pair of nodes meets on one of these relays, stays on its nearest and lets two of them federate, holds several at once, or punches a direct path and keeps them as standbys. Every relay host also runs a hosted exit, published in a signed map of its own. Relay modes

What you will not see here

Private and on-premises nodes stay private.

Organization-only relays run the same software and are pinned in customer configuration without being published to nexusatlas.net. They will not appear on this page, even when a node holds them alongside the public relays and the election ranks both on one scale.

Private deployment options
Get early access

Bring us the network you cannot control.

Apply as a pilot partner if you have a deployment ready to test, or start evaluating Nexus Atlas Traversal as a future customer. Tell us enough to understand the endpoints, carriers, regions, and operational constraints involved.

01

Pilot partner

Run an early deployment with direct engineering contact and help shape priorities through real-world feedback.

02

Customer evaluation

Research architecture, security, deployment options, and commercial fit before committing to a pilot.

Already enrolled? Open the console
Early-access applicationUsually answered by the product team

Your application is sent to the Nexus Atlas product team. You can also email office@nexusatlas.io.