On inferring autonomous system relationships in the internet
IEEE/ACM Transactions on Networking (TON)
Observation and analysis of BGP behavior under stress
Proceedings of the 2nd ACM SIGCOMM Workshop on Internet measurment
BGP routing stability of popular destinations
Proceedings of the 2nd ACM SIGCOMM Workshop on Internet measurment
Topology inference from BGP routing dynamics
Proceedings of the 2nd ACM SIGCOMM Workshop on Internet measurment
Power laws and the AS-level internet topology
IEEE/ACM Transactions on Networking (TON)
Identifying BGP routing table transfers
Proceedings of the 2005 ACM SIGCOMM workshop on Mining network data
Quantifying path exploration in the internet
Proceedings of the 6th ACM SIGCOMM conference on Internet measurement
PHAS: a prefix hijack alert system
USENIX-SS'06 Proceedings of the 15th conference on USENIX Security Symposium - Volume 15
Understanding slow BGP routing table transfers
Proceedings of the 9th ACM SIGCOMM conference on Internet measurement conference
Identifying BGP routing table transfers
Computer Networks: The International Journal of Computer and Telecommunications Networking
A cascading failure model for interdomain routing system
International Journal of Communication Systems
Improving the reliability of inter-AS economic inferences through a hygiene phase on BGP data
Computer Networks: The International Journal of Computer and Telecommunications Networking
| Hi-index | 0.00 |
BGP routing data collected by RouteViews and RIPE RIS have become an essential asset to both the network research and operation communities. However, it has long been speculated that the BGP monitoring sessions between operational routers and the data collectors fail from time to time. Such session failures lead to missing update messages as well as duplicate updates during session re-establishment, making analysis results derived from such data inaccurate. Since there is no complete record of these monitoring session failures, data users either have to sanitize the data discretionarily with respect to their specific needs or, more commonly, assume that session failures are infrequent enough and simply ignore them. In this paper, we present the first systematic assessment and documentary on BGP session failures of RouteViews and RIPE data collectors over the past eight years. Our results show that monitoring session failures are rather frequent, more than 30% of BGP monitoring sessions experienced at least one failure every month. Furthermore, we observed failures that happen to multiple peer sessions on the same collector around the same time, suggesting that the collector's local problems are a major factor in the session instability. We also developed a web site as a community resource to publish all session failures detected for RouteViews and RIPE RIS data collectors to help users select and clean up BGP data before performing their analysis.