Global edge network

rstream projects can now run with either Regional or Global routing. A Regional project stays attached to one selected region. A Global project exposes one common edge address and directs each connection to a nearby healthy region. Global routing is available to Pro and Enterprise projects, while Basic projects remain Regional.

Within a Global project, a connection can follow one of two paths. With Direct routing, the agent connects to the region that accepted the incoming connection, keeping application traffic on the shortest available path. With Cross-region routing, the agent remains attached to its selected region while rstream carries the connection between regions. Direct routing is the default, and same-region connections always stay Direct.

A tunnel can allow Cross-region routing when agent locality must remain stable. Agents use the Global endpoint by default, while the CLI can select an eligible region explicitly when locality or deployment constraints require it. Connection logs identify the path used and the regions involved.

Regional and Global projects support the same published and private tunnel protocols, WebTTY sessions, and managed TURN services.

See Global and Regional Routing for project scope, region selection, routing paths, and protocol behavior.