Routing tables
STACKIT introduces routing tables as part of a new networking feature. Routing tables provide greater flexibility and control over how network traffic flows within a STACKIT network area (SNA). This feature is available as a public preview.
Routing tables overview
Section titled “Routing tables overview”A routing table is a collection of routes that define how traffic moves between networks, services, and external systems. You configure routing tables at the network architecture level and apply them to any routed network within the same environment. Each STACKIT network area includes one default routing table. STACKIT creates this table automatically when you create a new environment. All routed networks follow the default table unless you assign a different one. You can define multiple routing tables per network area. One network can use only one routing table at a time, but you can assign a single routing table to multiple networks. Routing tables determine the path that outbound traffic takes from a service or network component. They do not control how inbound traffic reaches the destination.
Preview scope and limitations
Section titled “Preview scope and limitations”Routing tables apply only to routed Layer 3 networks in a STACKIT Network Area (SNA). They don’t affect traffic between endpoints on the same Layer 2 network. STACKIT provides a default routing table for each SNA. You can’t delete this table. To learn more about configuration options, see the routing tables specification. Because this feature is in public preview, its behavior may change.
Route types and priorities
Section titled “Route types and priorities”Routing tables consist of different types of routes serving different purposes and having a different priority in the overall routing context. Route types with a higher priority value are preferred over lower priority ones if they have the same prefix length. If routes of the same route type have the same prefix length, equal-cost-multi-path (ECMP) is performed.
| priority | route type | description |
|---|---|---|
| 3 | system routes | System routes are automatically generated routes for connectivity between projects inside an SNA. System routes are enabled by default for routing tables but can be disabled to manage traffic and isolation within a network environment. |
| 2 | static routes | Static routes are routes which are added by a user. They can have different next-hops such as an IP-address, blackhole or the internet. |
| 1 | dynamic routes | Dynamic routes are routes which are learned through a dynamic routing protocol like BGP. Dynamic routes are enabled by default for routing tables but can be disabled. |
Limits
Section titled “Limits”The following limits apply:
- Up to 20 routing tables per network area
- Up to 50 routes per routing table
Enabling routing tables
Section titled “Enabling routing tables”When creating a new SNA you can already enable the new routing tables by using the label preview/routingtables=true.
If you want to migrate an existing SNA to routing tables please contact the STACKIT Help Center.
Migration plan
Section titled “Migration plan”In the first half of 2026, STACKIT will migrate all static routes in existing environments into the default routing table. This change helps standardize routing behavior across your environment.
Once migrated, your SNA’s static routes are transferred to the default routing table. We recommend you to use routing tables for all future management. While the static routes endpoints will still work for basic management of the default routing table, they will become unavailable if you configure unsupported routes (like blackhole or internet routes) in the default table.
For more information on that topic, contact STACKIT Help Center.
Looking ahead
Section titled “Looking ahead”STACKIT plans to integrate dynamic routing features into routing tables. Upcoming enhancements include support for learned routes from the VPN service and future STACKIT products. These changes will unify routing control across services.