Quantifying the Pitfalls of Traceroute in AS Connectivity Inference

  • Yu Zhang
  • Ricardo Oliveira
  • Hongli Zhang
  • Lixia Zhang
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6032)


Although traceroute has the potential to discover AS links that are invisible to existing BGP monitors, it is well known that the common approach for mapping router IP address to AS number (IP2AS) based on the longest prefix matching is highly error-prone. In this paper we conduct a systematic investigation into the potential errors of the IP2AS mapping for AS topology inference. In comparing traceroute-derived AS paths and BGP AS paths, we take a novel approach of identifying mismatch fragments between each path pair. We then identify the origin and cause of each mismatch with a systematic set of tests based on publicly available data sets. Our results show that about 60% of mismatches are due to IP address sharing between peering BGP routers in neighboring ASes, and only about 14% of the mismatches are caused by the presence of IXPs, siblings, or prefixes with multiple origin ASes. This result helps clarify an argument that comes from previous work regarding the major cause of errors in converting traceroute paths to AS paths. Our results also show that between 16% and 47% of AS adjacencies in two public repositories for traceroute-derived topology are false.


AS topology measurement traceroute BGP 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Archipelago Measurement Infrastructure,
  2. 2.
    Internet Routing Registry,
  3. 3.
    RIPE routing information service project,
  4. 4.
    RouteViews routing table archive,
  5. 5.
    UCLA IRL Internet topology collection,
  6. 6.
    Augustin, B., Cuvellier, X., Orgogozo, B., Viger, F., Friedman, T., Latapy, M., Magnien, C., Teixeira, R.: Avoiding traceroute anomalies with paris traceroute. In: IMC 2006 (2006)Google Scholar
  7. 7.
    Chang, H., Jamin, S., Willinger, W.: Inferring AS-level Internet topology from router-level path traces. In: SPIE ITCom (2001)Google Scholar
  8. 8.
    Hunt, J.W., Mcllroy, M.D.: An algorithm for differential file comparison. Tech. rep., Bell Laboratories (1976)Google Scholar
  9. 9.
    Hyun, Y., Broido, A., Claffy, K.C.: On third-party addresses in traceroute paths. In: Proc. of Passive and Active Measurement Workshop, PAM (2003)Google Scholar
  10. 10.
    Hyun, Y., Broido, A., Claffy, K.C.: Traceroute and BGP AS path incongruities. Tech. rep., CAIDA (2003)Google Scholar
  11. 11.
    Madhyastha, H., Isdal, T., Piatek, M., Dixon, C., Anderson, T., Krishnamurthy, A., Venkataramani, A.: iPlane: an information plane for distributed services. In: Proc. of OSDI (2006)Google Scholar
  12. 12.
    Mao, Z.M., Johnson, D., Rexford, J., Wang, J., Katz, R.H.: Scalable and accurate identification of AS-level forwarding paths. In: INFOCOM 2004 (2004)Google Scholar
  13. 13.
    Mao, Z.M., Rexford, J., Wang, J., Katz, R.H.: Towards an accurate AS-level traceroute tool. In: Proc. of ACM SIGCOMM (2003)Google Scholar
  14. 14.
    Oliveira, R., Pei, D., Willinger, W., Zhang, B., Zhang, L.: In search of the elusive ground truth: The Internet’s AS-level connectivity structure. In: Proc. ACM SIGMETRICS (2008)Google Scholar
  15. 15.
    Oliveira, R., Zhang, B., Zhang, L.: Observing the evolution of Internet AS topology. In: ACM SIGCOMM (2007)Google Scholar
  16. 16.
    Shavitt, Y., Shir, E.: DIMES: Let the Internet measure itself. ACM SIGCOMM Computer Comm. Review, CCR (2005)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Yu Zhang
    • 1
  • Ricardo Oliveira
    • 2
  • Hongli Zhang
    • 1
  • Lixia Zhang
    • 2
  1. 1.Harbin Institute of TechnologyHarbinChina
  2. 2.University of CaliforniaLos AngelsUSA

Personalised recommendations