Leverage Network Bandwidth Costs

Noction IRP can evaluate routing decisions through both performance and commercial policy. When cost control is required, IRP can prioritize providers according to their configured cost, commit, and precedence structure while still avoiding paths that violate acceptable performance conditions. This allows operators to use lower-cost bandwidth more aggressively without blindly pushing traffic onto a cheaper but poorly performing path.

IRP monitors provider utilization and can automatically move selected outbound traffic away from a provider that is approaching or exceeding its defined bandwidth target. Instead of requiring engineers to manually adjust local preference, route maps, or provider prepends during peak periods, IRP applies targeted BGP improvements for eligible prefixes and shifts traffic toward providers with available headroom.

Yes. IRP can group providers and distribute traffic according to their relative commercial or capacity targets rather than forcing an equal split. This is important when one upstream has a larger commit, another has a smaller commit, and a third is intended only as a secondary or overflow path. IRP’s provider grouping and precedence logic allow bandwidth utilization to follow business intent instead of raw BGP preference alone.

IRP can treat multiple provider links as part of a logical group when bandwidth should be managed against a combined commercial objective. This helps avoid unnecessary route changes when one physical link is temporarily higher, but the provider group remains within the intended aggregate usage. It also allows operators to manage capacity based on how the bandwidth is billed, not only on how interfaces are physically connected.

For inbound bandwidth control, IRP uses BGP-based traffic-engineering methods to influence how external networks select paths toward the operator’s prefixes. It can adjust how network segments are advertised to upstream providers, typically by manipulating AS-path prepending, so more ingress traffic leans toward preferred providers and less enters through providers that are above their intended utilization level.

Static prepending is usually coarse and manual: an engineer decides which prefix to prepend toward which provider and then waits to see what happens. IRP automates this process by monitoring inbound utilization, estimating the effect of advertisement changes, and adjusting prefix announcements according to bandwidth objectives. This makes inbound shaping more adaptive and less dependent on manual trial-and-error.

IRP’s transiting traffic optimization extends the inbound bandwidth-control model to traffic that is not simply originated by the local network. When traffic is entering through an undesirable interface, IRP can influence Internet-wide best-path selection by increasing AS-path length for the prefix associated with that traffic. This helps networks that carry downstream, customer, or third-party traffic keep transit flows aligned with commercial and operational objectives.

Global Commit is designed for organizations that operate multiple locations or IRP instances but buy bandwidth under a shared provider agreement. IRP can coordinate local, regional, and global utilization objectives so one site does not exceed its practical bandwidth target while another site leaves paid capacity unused. This is useful when each location has independent routing, but the commercial commitment is negotiated globally.

In a multi-site deployment, Global Commit can account for locally reserved bandwidth while still coordinating usage across the broader provider agreement. This allows each location to maintain operational headroom for local demand while making unused capacity visible to the wider global commit strategy. The result is a more controlled balance between local resilience and global cost efficiency.