Atlas selects relays using observed network performance, not a marketing region label. Every published relay is externally verified, cryptographically identified and removable from the map when it becomes stale.
Illustrative sample data—not a public status or SLA statement.
Relays self-register with region, addresses, version and identity. The control plane probes the claimed addresses from outside and only publishes a relay after successful verification.
Accurate mapping classification requires different destination IP addresses—not merely two ports. A relay with two public addresses can serve as a complete STUN observation pair.
Candidate relays are probed and peer pairs can deterministically converge on the same best shared set. A direct path remains additional to the configured relay count.
Heartbeats report liveness and load to the operator console, and a stale relay is dropped from the next signed map the operator mints — the map is signed outside the serving control plane, so publication changes are a deliberate operator action, never a server-side one. Established Atlas paths and cached maps remain independent of the directory either way.
Static relay configuration remains available even when automatic discovery is enabled, allowing public, private and mixed relay estates.
Use the signed public relay inventory and measured relay selection with no relay servers to operate.
Pin relay addresses and identities in configuration for sovereign or closed operational environments.
Keep an organization-controlled relay beside hosted geographic redundancy and direct connectivity.
Dedicated relay and observation nodes can run in your cloud accounts, data centres, field sites, or isolated operational zones. They are configured only for authorized Atlas nodes, are not published in the public signed map, and do not appear on the public live-network page.
Organizations can use a fully private estate or combine it with public geographic redundancy and direct paths. Identity pinning keeps trust independent of DNS and IP ownership in either model.
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.
Run an early deployment with direct engineering contact and help shape priorities through real-world feedback.
Research architecture, security, deployment options, and commercial fit before committing to a pilot.
