Skip to Content
[CAIDA - Center for Applied Internet Data Analysis logo]
Center for Applied Internet Data Analysis
CAIDA Internet eXchange Points (IXPs) Dataset
This dataset provides information about Internet eXchange Points (IXPs) and their geographic locations, facilities, prefixes, and member ASes. It is derived by combining information from PeeringDB, Hurricane Electric, Packet Clearning House (PCH), Wikipedia, BGP Looking Glass, and GeoNames.
|   Access the IXPs Dataset   |

An Internet eXchange Point (IX or IXP) is a physical infrastructure used by Internet service providers (ISPs) and content delivery networks (CDNs) to exchange Internet traffic between their networks (Autonomous Systems - ASes). IXPs are located in numerous data centers, aka facilities, and a single facility can contain mutliple IXPs. Each IXP has a prefix, or collection of prefixes, which is used by companies/ASes to address machines within the IXP infrastructure. An AS connected to a given IXP is known as a member of that IXP. Internet traffic exchange through an IXP makes use of Border Gateway Protocol (BGP) that recognizes ISPs and CDNs by their Autonomous System Numbers (ASNs).

Sources of Data

In order to make the most complete list of IXPs we combined information available from the following sources:


First, we downloaded the GeoNames data set and created a local sqlite database of geographic coordinates indexed on the name, asciiname, and alternative names of cities and villages. If we could not find a match between the name of the city where a certain IXP is located and any of the location strings in the database, we assigned negative geo_ids to those IXPs.

Next, we tried to identify the cases when IXPs listed in the different data sources are in fact the same. This is a non-trivial task since IXPs names, cities and addresses could be (and are) spelled differently. We calculated the Levenshtein distance between names and addresses of all IXPs located in the same city. IXPs with the names more than 4 characters long and for which the distance was less than 2, not determined by the first or last characters of each string, were assumed to be identical.


All files are in JSONL (JSON Lines) format with comment lines starting with '#' and all other lines containing a single object in JSON format. JSONL can be converted to JSON with tool. All files begin with a commented meta data line showing when the file was generated.

File ixs.jsonl contains information about individual IXPs. The "pch_id", "pdb_id", and "pdb_org_id" values match the IXP ids in the original sources, Packet Clearing House (PCH) and PeeringDB (PDB) respectively. Other fields are self-explanatory.

    "ix_id": 15,
    "name": "AMPATH - Florida International University/CIARA",
    "alternatenames": [
        "CoreSite - Any2 Miami",
        "NAP Miami"
    "city": "Miami",
    "region": "Florida",
    "country": "US",
    "geo_id": 4164138,
    "org_id": 3,
    "pch_id": 306,
    "pdb_id": 205,
    "pdb_org_id": 34,
    "sources": [
    "url": [

File facilities.jsonl contains information about individual facilities. The "clli" value is CLLI name or a COMMON LANGUAGE Location Identifier Code, an identifier used within the North American telecommunications industry. Other fields are self-explanatory.

    "fac_id": 0,
    "name": "Equinix Ashburn (DC1-DC11)",
    "address": "21715 Filigree CtBuilding F",
    "alternatenames": [],
    "city": "Ashburn",
    "region": "VA",
    "clli": "ASBNVA",
    "country": "US",
    "zipcode": "20147-6205"
    "latitude": 39.016363,
    "longitude": -77.459023,
    "org_id": 0,
    "pdb_fac_id": 1,
    "pdb_org_id": 2,
    "sources": [

File ix-facilites.jsonl contains mapping between facilities and IXPs.

    "fac_id": 286,
    "ix_id": 404

File ix-asns.jsonl shows IP addresses used at a given IXP by each member AS.

    "asn": "AS1916",
    "ipv4": [
    "ipv6": [
    "ix_id": 705,
    "sources": [

File ix-prefixes.jsonl shows which IXPs are announcing which prefixes. The protocol value is either 4 or 6 corresponding to IPv4/IPv6 networks.

    "ix_id": 133,
    "network": "2001:13c7:6001::/48",
    "protocol": 6,
    "sources": [

File organizations.jsonl contains the information about each organization learned from PDB. These can be matched with their corresponding facility by matching the facility's pdb_org_id with the organization's pdb_org_id.

    "address": "One Lagoon Drive",
    "city": "Redwood City",
    "country": "US",
    "org_id": 0,
    "pdb_org_id": 2,
    "region": "CA",
    "url": "",
    "zipcode": "94065"

File locations.jsonl is similar to the geoname locations, but contains negative "geo_id"s for those locations where geographic locations of IXPs were not found in the geonames dataset.

    "admin1_code": "60",
    "admin2_code": "V",
    "admin3_code": "46119",
    "admin4_code": "",
    "alternatenames": [
    "asciiname": "L'Enova",
    "cc2": "",
    "country_code": "ES",
    "dem": 46,
    "elevation": 0,
    "feature_class": "P",
    "feature_code": "PPL",
    "geo_id": 2517989,
    "geoname_id": 2517989,
    "latitude": 39.05,
    "longitude": -0.48333,
    "name": "L'\u00c8nova",
    "population": 997

Data Access

Access to these data is subject to the terms of the following CAIDA Acceptable Use Agreement (printable version in PDF format)

As required by the AUA, if you use this dataset in any publication (including but not limited to: papers, presentations, web pages, and papers published by a third party) please include the following reference:

The CAIDA UCSD IXPs Dataset, <date range used>
Also, please report your publication to CAIDA.

  Last Modified: Fri Feb-9-2018 17:13:04 PST
  Page URL: