A network connectivity configuration in which a single routing domain (AS or prefix holder) maintains active BGP sessions with two or more upstream providers or peers so that it can advertise its prefixes via multiple paths for redundancy, resilience, load distribution, or traffic engineering.

Principle

Multiple upstream connections increase path diversity and reduce single‑provider dependency, but actual resilience and inbound/outbound traffic control depend on configured BGP policy (export/import filters, AS‑path manipulation, local preference) and on whether the network holds provider‑independent addressing.

Demonstration

Illustrative scenario → An enterprise establishes BGP sessions with Provider A and Provider B and advertises its prefixes to both. It uses AS‑path prepending toward B to influence inbound traffic and local‑preference settings for outbound selection. If Provider A fails, Provider B continues to carry announced prefixes, preserving reachability subject to BGP convergence.

Misapplication

Mistaken interpretation: assuming connecting physical links to multiple providers always yields full redundancy. Semantic error: ignoring the need for BGP configuration, unique addressing (provider‑independent space), or acceptance by peers—physical multihoming without proper routing/policy may not prevent reachability loss.

Consequence

Multihoming improves availability and offers traffic‑engineering flexibility but raises operational complexity (BGP policy, monitoring), may incur higher costs, and can increase global routing table size if it leads to deaggregation or advertisement of multiple independent prefixes.

Reversal

Qualification: multihoming may be ineffective when upstream providers refuse to accept certain prefixes, when only provider‑aggregated address space is used, or when physical common‑mode failures exist; in those cases multihoming does not materially improve resilience.

Boundary

Clearly within: an AS with simultaneous BGP sessions to two independent transit providers advertising the same prefixes. Boundary case: multiple physical links to the same provider (not independent multihoming) or single‑provider multi‑path. Clearly outside: a backup layer‑2 link without independent BGP sessions.

Semantic Tension

Resilience and traffic control ↔ operational cost and routing ecosystem impact: networks gain redundancy and control at the expense of increased configuration complexity, cost, and potential contribution to routing table growth.

Synthesis

Multihoming is a trade‑off: it offers measurable improvements in reachability and control only when paired with correct routing policies and appropriate address management; otherwise apparent redundancy can be illusory and can impose broader operational costs.