{"id":22951,"date":"2026-08-24T08:49:43","date_gmt":"2026-08-24T06:49:43","guid":{"rendered":"https:\/\/www.savecall.de\/multicloud-scheitert-am-netz-darunter-wie-direkte-cloud-zu-cloud-pfade-latenz-senken-savecall-vergleicht-80-carrier-neutral\/"},"modified":"2026-11-12T11:43:46","modified_gmt":"2026-11-12T10:43:46","slug":"multicloud-connectivity-why-your-network-is-becoming-the-bottleneck","status":"publish","type":"post","link":"https:\/\/www.savecall.de\/en\/multicloud-connectivity-why-your-network-is-becoming-the-bottleneck\/","title":{"rendered":"Multicloud Connectivity: Why Your Network Is Becoming the Bottleneck"},"content":{"rendered":"\n

\n

\n

Multicloud Connectivity: Why Your Network Is Becoming the Bottleneck<\/h1>\n<\/div>\n\n\n\n

Trusted Advisor for IT & Telecommunications Sourcing<\/h3>\n<\/div>\n\n\n\n
\n
\n
Direct. Controlled. Scalable.<\/h2>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n
Multicloud Connectivity<\/h2>\n\n\n\n
Multicloud rarely fails because of the cloud, but because of the network between the clouds.<\/h6>\n\n\n\n
More and more companies are distributing their workloads across several public clouds. What makes sense from a procurement and resilience perspective shifts complexity to where it is least visible: the corporate network<\/a>. When applications constantly exchange data across cloud boundaries, the quality of the connection decides whether a multicloud strategy delivers on its promise.<\/p>\n\n\n\n
<\/div>\n\n\n\n
The difference lies not in the number of contracts, but in the architecture underneath. Treating connectivity as the sum of individual procurement processes produces exactly the fragmentation that costs performance, opens security gaps and drives up operating effort. This article shows where the typical breaking points lie and which architectural approaches eliminate them.<\/p>\n\n\n\n
\n
<\/div>\n\n\n\n
\n
\n
Consultation<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
Table of Contents<\/h3>\n\n\n\n
\n
Multicloud is the norm, cross-cloud the next stage<\/a><\/li>\n\n\n\n
Why classic network architectures reach their limits<\/a><\/li>\n\n\n\n
What fragmentation really costs in operations<\/a><\/li>\n\n\n\n
Multicloud networking instead of many individual solutions<\/a><\/li>\n\n\n\n
Security becomes enforceable instead of fragmented<\/a><\/li>\n\n\n\n
What an integrated multicloud approach delivers<\/a><\/li>\n\n\n\n
How Savecall supports you<\/a> <\/li>\n\n\n\n
Conclusion<\/a><\/li>\n\n\n\n
FAQ<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
<\/div>\n<\/div>\n\n\n\n
\n
Multicloud is the norm, cross-cloud the next stage<\/h3>\n\n\n\n
<\/div>\n\n\n\n
A company is said to have a multicloud strategy as soon as it uses more than one public cloud provider. In practice, this has now become the rule: the clear majority of companies running hybrid cloud operations use several public cloud services.<\/p>\n\n\n\n
The reasons are mostly functional. A CRM runs where it was historically set up. Analytics and AI workloads move to wherever the platform offers the better services. Each cloud takes on what it does best.<\/p>\n\n\n\n
A number of organisations are now going one step further and distributing individual applications or workloads across several clouds, a cross-cloud approach. The benefit is twofold: the application remains available if one platform fails, and price differences between providers can be exploited dynamically. The prerequisite, however, is that the distributed components can communicate with each other with minimal delay.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Why classic network architectures reach their limits<\/h3>\n\n\n\n
<\/div>\n\n\n\n
Multicloud environments generate continuous east-west traffic between the platforms, for example when an e-commerce application constantly synchronises with CRM and ERP systems. It is precisely this traffic that traditional network concepts serve poorly.<\/p>\n\n\n\n
Hub-and-spoke architectures route cloud-to-cloud traffic via a central node, usually the company’s own data centre. This backhauling creates latency that becomes immediately noticeable in latency-sensitive applications, in application performance as well as in user perception. What multicloud environments need instead are direct paths: between the clouds themselves and between the cloud and on-premises resources. For cross-cloud scenarios, this is not an optimisation, but a basic requirement.<\/p>\n\n\n\n
Almost all hyperscalers offer dedicated connections between company sites and the cloud. Cloud onramps<\/a> for DIA, Ethernet or leased line connections are well established. Direct connections between the cloud platforms themselves, on the other hand, are much rarer, and their availability varies considerably by region and provider.<\/p>\n\n\n\n
The obvious way out, VPN tunnels between the clouds, is rarely viable: costs rise with volume, and the available bandwidth is often not enough for productive data flows. What remains is a patchwork of individual services from different providers, each procured on a case-by-case basis. That works until the sum of the individual solutions itself becomes the problem.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What fragmentation really costs in operations<\/h3>\n\n\n\n
<\/div>\n\n\n\n
Every cloud platform brings its own network and security model: its own tools, its own concepts, its own know-how. With each additional platform, this effort does not grow linearly, but disproportionately. IT teams then manage parallel worlds that can neither be automated together nor monitored uniformly.<\/p>\n\n\n\n
The consequences are measurable. Only about half of companies describe routing traffic across several cloud providers as straightforward, and load balancing looks hardly any better. In concrete terms, three cost blocks arise:<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
Operating effort and lack of consistency<\/strong> due to parallel tool landscapes for each platform<\/li>\n\n\n\n
Blind spots in monitoring<\/strong> that make bottlenecks visible too late<\/li>\n\n\n\n
Inconsistent security policies,<\/strong> because each platform uses its own policy models<\/li>\n\n\n\n
More difficult compliance obligations<\/strong> under GDPR, NIS2 and industry-specific requirements<\/li>\n<\/ul>\n\n\n\n<\/div>\n\n\n\n
Without end-to-end transparency across all connections, troubleshooting becomes detective work. Capacities are sized incorrectly, and cost optimisation remains guesswork instead of control.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Multicloud networking instead of many individual solutions<\/h3>\n\n\n\n
<\/div>\n\n\n\n
Multicloud networking platforms address exactly this point. They connect all cloud environments directly with each other and with on-premises resources, and make these connections manageable via a common control layer. In practice, this means: all sites of a corporate WAN reach the cloud via a central transit gateway, while the clouds are directly connected to each other. Unnecessary backhauling is eliminated.<\/p>\n\n\n\n
Many of these platforms are based on SD-WAN<\/a>. The approach reduces complexity by unifying the entire network infrastructure and bringing together a wide range of connection types: DIA, business internet, Ethernet and mobile via central control. Traffic is automatically routed by application priority, without rules having to be maintained separately for each site.<\/p>\n\n\n\n
Equally important is end-to-end visibility across all connections. Faults can be isolated faster, capacities adjusted proactively, problems solved before users notice them, and costs assessed reliably instead of overprovisioning. A uniform, software-defined environment also reduces the error rate in configurations and enables redundant paths with automatic failover.<\/p>\n\n\n\n
<\/div>\n\n\n\n
$\"Cloud$ <\/figure>\n\n\n\n
<\/div>\n\n\n\n
Security becomes enforceable instead of fragmented<\/h3>\n\n\n\n
<\/div>\n\n\n\n
The security dimension weighs heaviest. Where each platform uses its own policy models, uniform security policies can hardly be enforced, and misconfigurations go undetected. More than half of companies consider securing cloud environments more demanding than securing classic on-premises infrastructure anyway. Each additional platform further enlarges the attack surface, which is why multi-cloud security<\/a> belongs in the architecture decision and not in follow-up work.<\/p>\n\n\n\n
A standardised architecture creates the prerequisite for a consistent level of security across the entire network. Vulnerabilities and misconfigurations become visible, attacks are detected earlier, and compliance evidence becomes much easier.<\/p>\n\n\n\n
Zero Trust and SASE concepts build on this: instead of one-time authentication at the perimeter, every access is checked continuously. This considerably limits the damage should an attacker ever gain a foothold.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What an integrated multicloud approach delivers<\/h3>\n\n\n\n
<\/div>\n\n\n\n
The result is a network environment that works consistently regardless of location and cloud provider and is prepared for future cloud projects instead of slowing them down. Specifically on five levels:<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
Performance:<\/strong> low latency for demanding cloud applications, no unnecessary backhauling<\/li>\n\n\n\n
Reliability:<\/strong> redundant paths, automatic failover, end-to-end transparency<\/li>\n\n\n\n
Security:<\/strong> uniform policies, Zero Trust and SASE integration, reliable compliance evidence<\/li>\n\n\n\n
Operations:<\/strong> central management of all connections instead of parallel tool landscapes<\/li>\n\n\n\n
Scalability:<\/strong> new clouds and sites can be added without breaking the architecture<\/li>\n<\/ul>\n\n\n\n<\/div>\n\n\n\n
The order remains decisive. An overlay can only control as well as the underlay allows. Anyone who introduces SASE and SD-WAN<\/a> without sizing the underlying lines and cloud onramps merely shifts the problem one level up.<\/p>\n<\/div>\n\n\n\n
\n
<\/div>\n<\/div>\n\n\n
<\/p>\n\n\n
\n
<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
How Savecall supports you <\/h3>\n\n\n\n
<\/div>\n\n\n\n
Savecall is a vendor-independent sourcing and consulting partner for telecommunications and network solutions, not a carrier, and therefore without a product agenda of its own. We design the right underlay of DIA, business internet, Ethernet, leased lines and cloud onramps, sized to what your workloads actually need, and assess overlay concepts such as SD-WAN, SASE and NaaS on a vendor-neutral basis.<\/p>\n\n\n\n
With access to more than 80 carrier partners worldwide, we compare prices, SLAs and availability across all regions and sites, even with growing network complexity<\/a>. On top of that come the consolidation of existing contracts, SLA improvements and support for ongoing operations, from the as-is analysis to contract optimisation.<\/p>\n\n\n\n
All major carriers worldwide. One portal. One SPOC. One invoice.<\/p>\n\n\n\n
<\/div>\n\n\n\n
$\"Global$ <\/figure>\n\n\n\n
<\/div>\n\n\n\n
Conclusion: The architecture decision comes before choosing a provider<\/strong><\/h3>\n\n\n\n<\/div>\n\n\n\n
Multicloud rarely fails because of the cloud, but because of the network underneath. The way out does not lie in more individual contracts, but in a well-thought-out architecture concept of underlay and overlay. The decisive question is therefore not which provider makes the best offer, but which architecture will meet the requirements of the coming years. Anyone planning a multicloud architecture or putting their existing cloud connectivity to the test should start with the architecture and only then talk about providers.<\/p>\n\n\n\n
\n
Consultation<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n
$\"\"$ <\/figure>\n<\/div>\n\n\n\n
\n
Written by<\/p>\n\n\n\n
Nikolaus von Johnston<\/h3>\n\n\n\n
CEO, SAVECALL<\/strong><\/p>\n\n\n\n
Leads SAVECALL as Managing Director and advises multi-site companies on sourcing and optimising their networks. His aim: to find the solution among more than 80 carriers that fits the customer technically and commercially.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
$\"SAVECALL$ <\/figure>\n\n\n\n
Kostenloser<\/span> Expertentermin<\/a><\/h3>\n\n\n\n
\n
Buchen<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
Sources<\/h3>\n\n\n\n
\n
https:\/\/www.flexera.com\/blog\/finops\/flexera-2026-state-of-the-cloud-report-the-convergence-of-cloud-and-value\/<\/a><\/li>\n\n\n\n
https:\/\/www.bsi.bund.de\/SharedDocs\/Downloads\/DE\/BSI\/Mindeststandards\/Mindeststandard_Nutzung_externer_Cloud-Dienste_Version_2_1.html<\/a><\/li>\n\n\n\n
https:\/\/csrc.nist.gov\/pubs\/sp\/800\/207\/final<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
Frequently Asked Questions about Multicloud Connectivity<\/h2>\n<\/div>\n<\/div>\n\n\n\n
What is the difference between multicloud and cross-cloud?<\/strong>
Multicloud means that a company uses more than one public cloud provider, usually with clearly separated applications for each platform. Cross-cloud goes one step further and distributes a single application or workload across several clouds. The benefit is twofold: the application remains available if one platform fails, and price differences between providers can be exploited dynamically. The prerequisite, however, is that the distributed components communicate with each other with minimal delay. Cross-cloud therefore places much tougher demands on the network architecture than classic multicloud.<\/p> <\/div>
Why is backhauling via your own data centre a problem?<\/strong>
Backhauling routes cloud-to-cloud traffic via a central node, usually the company’s own data centre, and thereby creates additional latency. In latency-sensitive applications, this detour becomes immediately noticeable, in application performance as well as in user perception. Multicloud environments generate continuous east-west traffic between the platforms, for example when an e-commerce application constantly synchronises with CRM and ERP systems. It is precisely this traffic that hub-and-spoke architectures serve poorly. Multicloud environments need direct paths between the clouds and to on-premises resources instead.<\/p> <\/div>
Are VPN tunnels between two clouds sufficient?<\/strong>
VPN tunnels between cloud platforms are the obvious way out, but rarely viable. Costs rise with the volume transferred, and the available bandwidth is often not enough for productive data flows. For occasional administrative access or test environments, a tunnel may be sufficient. For permanent east-west traffic between productive workloads, it is the wrong foundation. Resilient multicloud architectures therefore rely on direct connections and a transit gateway instead of a growing number of individual tunnels.<\/p> <\/div>
What is a transit gateway in a multicloud architecture?<\/strong>
A transit gateway is the central handover point through which all sites of a corporate WAN reach the cloud. The clouds themselves are directly connected to each other, so that unnecessary backhauling via the data centre is eliminated. The advantage lies in controllability: routing, prioritisation and security policies are maintained in one place instead of separately for each platform. New clouds and sites can thus be added without breaking the architecture. The gateway is therefore less a product than an architecture decision.<\/p> <\/div>
What role do SD-WAN and SASE play in multicloud connectivity?<\/strong>
SD-WAN is the technical foundation of many multicloud networking platforms. It unifies different connection types such as DIA, business internet, Ethernet and mobile via central control and automatically routes traffic by application priority. SASE builds on this foundation and moves security functions into the network layer, so that every access is checked continuously instead of only once at the perimeter. Together, both create a consistent level of security across all clouds and sites. The underlay on which both are built remains decisive.<\/p> <\/div>
How does Savecall support multicloud connectivity?<\/strong>
Savecall is not a carrier, but a vendor-independent sourcing and consulting partner for network solutions. With more than 80 carrier partners worldwide, Savecall supports the design of the right underlay, meaning DIA, business internet, Ethernet, leased lines and cloud onramps, sized to what the workloads actually need. Overlay concepts such as SD-WAN, SASE and NaaS are compared on a vendor-neutral basis instead of being tied to one ecosystem. On top of that come price and performance comparisons across all regions, contract optimisation and one point of contact for ongoing operations.<\/p> <\/div> <\/div>\n\n\n\n
\n
\n
Articles You Might Also Like<\/h2>\n<\/div>\n\n\n\n
\r\n
\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Internet<\/p>\r\n <\/div>\r\n\r\n
\r\n
5 Effects of a network failure<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"WAN$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
4 signs that your network is ready for digital transformation<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Mobile radio management<\/p>\r\n <\/div>\r\n\r\n
\r\n
Hybrid working – how it works!<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Security<\/p>\r\n <\/div>\r\n\r\n
\r\n
With SD-WAN and SASE: a digital workplace that inspires!<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
11 steps to network transformation with SD-WAN<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Security<\/p>\r\n <\/div>\r\n\r\n
\r\n
3 things you need to know about SASE and SD-WAN<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"WAN$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
The challenge of introducing SD-WAN<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"WAN$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
5 advantages of SD-WAN networks – briefly summarized<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"Das$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
IPSEC shutdown in China<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"Das$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
“Great Firewall of China” – VPN to China<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"Das$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
Is China paralyzing VPN access for companies?<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
Innovation in a flexible and secure corporate network<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
SD-WAN – simply explained<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Internet<\/p>\r\n <\/div>\r\n\r\n
\r\n
Digital transformation: Network edge<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n <\/div>\r\n\r\n
\r\n
Business fiber optics Munich<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
Security<\/p>\r\n <\/div>\r\n\r\n
\r\n
Does your corporate network fulfill your business ambitions?<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
A specialist’s guide to your SD-WAN journey<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"Das$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
ki network determinism variance<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n
\r\n \r\n\r\n
\r\n
\r\n $\"SAVECALL$ <\/div>\r\n
WAN<\/p>\r\n <\/div>\r\n\r\n
\r\n
Global Connectivity from a Single Source<\/h3>\r\n
\r\n
Learn moreLearn more<\/h3>\r\n <\/div>\r\n <\/div>\r\n\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n\r\n
<\/div>\r\n
<\/div>\r\n
<\/div>\r\n<\/div>\r\n\r\n