IRP’s probing mechanism has been enhanced as well. The system Explorer – responsible for evaluating provider performance, uses trace routes for diagnosis of PBR policies and for outage detection. Depending on the current load, the provider’s router may not be able to respond to IRP’s requests. To overcome this, in IRP 2.5, the interval of these requests is automatically adjusted according to the router’s response rate, for more efficient querying.
In order to efficiently probe the destinations prefixes, the Explorer uses a registry with all the responsive IPs gathered from the edge router. IRP 2.5 has been equipped with a self-cleaning mechanism that removes the outdated IPs from this registry avoiding accumulation of data that could slow down the platform’s operation.
Moreover the new product version brings improvements to the system’s dashboard, reports and filters as well as a series of bug-fixes that makes the platform even more stable.