{
  "id": 19450189,
  "title": "The Third Cloud Breaks Your Peering Model: Transitive Routing and the Hub Decision",
  "url": "https://urgent.news/2026/11/11/the-third-cloud-breaks-your-peering-model-transitive-routing-and-the",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-11T05:23:15.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/onelifevibe/the-third-cloud-breaks-your-peering-model-transitive-routing-and-the-hub-decision-469b"
  },
  "original_language": "en",
  "account": "As a multi-cloud network expands beyond two clouds, connectivity becomes increasingly complex. Connecting a third cloud, often through acquisition or a specific workload, can break the existing network design. Peering between networks is not transitive, meaning a direct connection is required between all networks, leading to a full mesh design. The number of connections needed grows rapidly with each new cloud added. Adding a hub-and-spoke design replaces the full mesh with a single transit point for each cloud network. While this simplifies the design, it introduces trade-offs in latency, blast radius, and cost. Cloud-native transit services offer quick adoption and native route propagation but limit the overall network. Self-managed routing provides full control but requires operational effort and testing. Managed overlay fabrics provide consistency across clouds but trade some provider-specific visibility. The key to a successful hub design is clear routing policy and validation at the hub before advertisement to prevent policy failures.",
  "summary": "Two clouds are easy to connect. A pair of private links, a handful of route tables, and traffic flows both ways. The design fits on a whiteboard and it works — until a third cloud arrives, usually through an acquisition, a GPU region that only exists on one provider, or a SaaS workload that had to live somewhere specific. That is the moment most multi-cloud networks quietly break. Not with an…",
  "key_points": [],
  "editors_take": "Scaling beyond two cloud providers forces a shift from simple peering to complex hub architectures that trade network simplicity for increased latency and operational overhead.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}