Intelligent Routing Blog


There are several route optimization techniques applied to networks distinguished by a single routing domain. The traditional approach requires network engineers to apply various routing policies and re-route the traffic manually. Fortunately, the traditional approach has alternatives that can automate the route optimization process.


Our customers ask repeatedly about the benefits IRP brings to their infrastructure. To address some of these questions we've compiled a few Overview Reports regarding Probes and Loss or Latency Improvements made by IRP during a specific time period. The numbers are aggregated synthetic high level figures based on historical data collected by IRP.


Conventional wisdom leads us to believe that interconnects between peering partners in an Exchange that is shorter will also be better than traditional links via transit providers. An Exchange by definition interconnects two peering partners' networks removing all other intermediaries between them and tries to simulate a direct point-to-point link that by definition is the shortest. Who could possibly think this might not be the best route? What route can be better than a one hop interconnect via an Exchange or direct peer-to-peer session?


The typical fully-meshed iBGP configuration of routers can become very difficult to manage in large networks. Because of the increasing numbers of iBGP sessions the possibilities of scaling are limited. Therefore, in a large network, the full-mesh requirement for iBGP can be a big challenge.


There are various techniques for optimizing traffic routing across multiple transit providers available in a network. However, there are some additional challenges when there are connections to Internet Exchanges within the multi-homed blend. When looking to choose the best performing peer to send the traffic through, the main challenge is figuring out the peer/s that can reach the destination and actively probing it/them for network performance metrics such as latency and packet loss.


Nowadays, the Internet is made-up of more than 45,000 active Autonomous Systems (ASes), each with a different complexity level and specific configurations. To accomplish efficient traffic flow, a packet must traverse reliable paths through several network nodes, before it reaches its final destination and since these are increasing with the size of the Internet, more network-level issues are likely to happen, causing traffic to flow through unreliable paths.


Inter-domain traffic engineering aims to optimize traffic performance, originating and terminating in different administrative domains. At the moment, Autonomous Systems exchange traffic via exterior gateway protocols, the standard one being BGP [BGP4]. BGP offers a wide range of options and attributes, such as route filtering, which can be efficiently used for inter-domain traffic engineering.


Service Provider's customers want to know the time frames they can expect a response and resolution from the provider when they submit a request for support. A Service Level Agreement or simply SLA is a contract between a Service Provider (vendor) and a customer, which stipulates and describes the details of the business relationship among the parties. There couldn’t be a better way for a Service Provider to stand out of the competition than promising guaranteed and timely response to customers.


There is a lot of confusion around the 95th percentile bandwidth metering. Therefore this blog posting is intended to provide you with detailed information about the 95th percentile and how it performs versus other bandwidth metering methods.


All organizations that depend on Internet for sales revenue or business continuity require internet redundancy. Downtime lowers productivity, yields losses and painfully affects the company’s reputation.

In this blog we describe how to setup Border Gateway Protocol (BGP) to get rid of multiple internet redundancy issues and generate significant results for your company.