
Global routing view · 01
The global view connects path-selection rules with node geography and active routes.
NORDPORT routing determines where a request goes after it reaches the edge, using hostname and path rules, health signals and origin selection.
Routing begins with the request attributes that NORDPORT is configured to evaluate, such as hostname and path.
Rules are applied in a defined order so an explicit match can select the intended service, region or origin without relying on an ambiguous default.
Origin selection connects the matched request to the application endpoint that should receive it when edge delivery is not sufficient.
Health information can remove an unhealthy path from consideration and allow traffic to use an available alternative when the service is configured for failover.
DNS, health monitors, origin pools and policy revisions all influence routing, so a route change must be reviewed as a complete path.

The global view connects path-selection rules with node geography and active routes.

The routing core shows how a policy set becomes a deterministic choice of the next path segment.

The route board treats a path as an operational object with state, dependencies and control points.

The network view highlights real traffic directions between regions and nodes.
Our team is ready to help with infrastructure and integrations.