- Static routes are manually defined.
- Ideal for small, secure networks.
- Predictable and efficient with resources.
- Requires manual updates.
- Dynamic routes are learned automatically from routing protocols (in DynamicLink, we use BGP).
- Ideal for large, changing networks.
- Scalable and automatic failover.
- Higher bandwidth usage and complexity.
Add static routes
Static routes define a fixed path to a destination network. Use them when you need a specific next-hop or interface (for example, for Cloud WAN or site-to-site routing). Next to Routes > Static Routes, click Add. Complete the following fields:| Field | Description |
|---|---|
| Destination | IP prefix to reach (IPv4 or IPv6), e.g. 192.168.1.0/24 or 10.0.0.0/8 |
| Type | IP Address for a normal next-hop route. Interface for a route to an interface. This is only supported for IPSec interfaces. |
| Distance | Route distance (priority) for the route. By default, this is 1. Set a higher distance to make the route less desirable, for example to make it a backup route. |
| Description | Optional note for this route. |
Dynamic routes (BGP)
Dynamic routes are learned from BGP neighbors (e.g. cloud gateways, data centers, or other networks). You do not “add” dynamic routes manually; you configure BGP and the Cloud Router learns and displays them. For more information, see Configure BGP for the Cloud Router.If dynamic routes are missing
- Confirm the BGP session is up (neighbor status in the BGP tab).
- Confirm the neighbor is advertising the expected prefixes (check Sent/Received in AWS, Azure, or your peer).
- Review route filters and policies that might block or filter advertisements.
Route selection and precedence
When several routes exist to the same destination, the Cloud Router typically:- Prefers static over dynamic routes.
- Uses longest prefix match (more specific prefix wins).
- Uses distance/metric to choose among same-type routes.