<p>Shaping enterprises' network path selection</p>
BGP is the core protocol for routing data across the internet. Enterprises can influence how their data traverses the public internet, but their control varies based on a few factors:
The direction of the data (incoming vs. outgoing).
Whether they own their AS or not.
When an enterprise connects directly to a local ISP (direct internet access), it has limited control. The ISP manages data routing, possibly redirecting it to the destination or to another ISP with direct access, depending on its peering setup and its commercial agreements with other ISPs and IP Transit Providers
If the enterprise has its own AS, it gains more control over data routing, deciding which IP Transit provider to use, contingent on the quality it offers for the intended destination. However, once the data is handed over to the IP Transit provider, the enterprise loses control over the network path beyond that point.
Enterprises have minimal control over incoming traffic routing. The path data takes is determined by routing decisions among network providers (AS) on the way to the local ISP or IP Transit providers if the enterprise possesses its own AS.
Connecting to SaaS platforms operates under the same principles. Enterprises with their own AS typically connect to one or more IP Transit providers, which, in turn, connect to the Cloud Service Provider (CSP) hosting the desired SaaS platform.
This connection can be established directly through peering between the IP Transit provider and the CSP or via upstream connections that the IP Transit provider has with other network providers.
In this context, BGP configuration influences the egress traffic path, determining the choice of IP Transit provider to route data to the SaaS destination, subsequently impacting other network providers used for reaching the destination.
For ingress traffic, CSP's peering configuration largely dictates the path, something enterprises can't control directly. Nevertheless, enterprises can influence their end of the communication path by managing peering configurations with their local IP Transit providers.
When enterprises connect to SaaS platforms rather than accessing local resources in their data centers, performance is significantly affected by network performance. This performance is primarily measured in terms of latency and packet loss, both of which are influenced by the network path.
As discussed earlier, network performance is a primary driver of SaaS performance. It's critical to address network issues, which are shaped by BGP peering between network providers. So, what can an enterprise do when experiencing SaaS performance degradation due to network problems?
At the peering level, options vary depending on whether the enterprise has its own AS number. Here's a summary of the options:
Issues encountered on
In case of direct internet access
In case enterprise has own AS
Egress traffic
Open a support ticket at the local ISP.
Open a support ticket to the CSP that delivers the SaaS platform or to the SaaS provider.
Change the BGP routing.
Change transit provider or establish a new peering.
Ingress traffic
Change ISP.
Stop announcing your prefixes to the worst IP Transit provider.
Change IP Transit Provider or establish an additional peering.
In the case of direct internet access, options for the enterprise are limited. Apart from selecting another provider, there isn't much more it can do, as it depends entirely on their provider's quality.
However, if the enterprise has its own AS number, its options significantly improve, giving it greater control over the situation. One solution is to establish new peerings.
As explained earlier, peering involves interconnections between networks. Enterprises typically peer with their local IP Transit providers due to their limited international reach. Having a direct connection to a specific destination improves the likelihood of routing traffic through this connection.
On the internet, numerous Internet Exchange Points managed by Internet Exchange Providers (IXPs) aggregate network interconnections. Any network connected to these points can directly peer with any other party on the same point, provided they have a mutual agreement.
Most CSPs connect to multiple internet exchange points and readily peer with those needing their traffic. This applies to enterprises using SaaS providers in the cloud.
One way for enterprises or local telco providers to access these internet exchanges is by using a remote peering provider like BICS.
BICS acts as a one-stop shop, facilitating connectivity from the enterprise's interconnection point with BICS to the internet exchange, negotiating contracts with the exchange, and providing 24x7 support for this connection.
Depending on the peering and network strategy of the SaaS provider, it might be possible to connect directly with the SaaS provider in the cloud using the direct cloud connectivity options they offer.
In cases where direct connection to a cloud provider's infrastructure is feasible, enterprises can do this under specific conditions. In all other scenarios, they will need to utilize a Cloud Connect partner of the cloud provider.
BICS is a partner with the top 5 major cloud service providers and can assist enterprises or ISPs serving enterprises with their direct connectivity needs transparently. Through a carrier-grade connectivity portal, connecting to major cloud providers becomes straightforward and can be activated in a few minutes and with a few clicks.
For information about BICS Remote Peering or Cloud Connectivity, please don't hesitate to contact us.
