• Peering Matrix Peering VLAN



    6
    9
    3
    9


    9
    0
    0
    9

    1
    0
    3
    1
    0

    1
    3
    3
    3
    5

    1
    6
    2
    9
    8

    2
    4
    8
    7
    5

    2
    5
    4
    5
    9

    2
    8
    9
    1
    7

    3
    2
    9
    3
    4

    3
    8
    9
    6
    5

    4
    1
    8
    8
    7

    4
    2
    7
    5
    5

    4
    3
    4
    1
    4

    4
    4
    3
    5
    8

    4
    8
    6
    3
    5

    4
    9
    9
    8
    1

    5
    0
    5
    2
    2

    5
    0
    6
    5
    5

    5
    0
    6
    7
    3

    5
    1
    0
    8
    8

    5
    6
    5
    1
    0

    5
    7
    7
    5
    8

    5
    7
    8
    6
    6

    5
    8
    0
    7
    3

    5
    8
    2
    9
    1

    6
    0
    0
    2
    2

    6
    0
    8
    9
    0

    6
    1
    3
    4
    9
    		1
    9
    9
    3
    3
    0
    		2
    0
    2
    1
    2
    0
    		2
    0
    7
    1
    7
    6
    Hurricane Electric 6939
    M247 Ltd 9009
    Yahoo! 10310
    Cloudflare 13335
    InterBox Internet 16298
    NovoServe B.V. 24875
    NedZone Internet BV 25459
    FIORD 28917
    Facebook Inc 32934
    HostIn 38965
    Prolocation 41887
    Datafiber Telecom B.V. 42755
    H2B Consulting BV 43414
    Kauno Technologijos Universitetas 44358
    PCextreme B.V. 48635
    WorldStream BV 49981
    Pocos bv 50522
    ITS HOSTED 50655
    Serverius network 50673
    A2B Internet 51088
    Source XS B.V. 56510
    Cloudbear 57758
    Fusix Networks B.V. 57866
    YISP 58073
    ColoCenter bv 58291
    Sona Business B.V. 60022
    CentralNic Anycast B 60890
    MaxiTEL Telecom B.V. 61349
    CentralNic Anycast A 199330
    Comsave 202120
    OPENFIBER B.V. 207176

    Notes on the Peering Matrix

    • bilat: 0, multilat: 527
    • Clicking the AS number in the table header will isolate that column. Clicking individual cells in the body will freeze the dynamic highlighting.
    • Where a member is not listed on this peering matrix, it is because they are currently not actively peering at , or because they have opted out of presenting their peering information in this database.
    • This peering matrix is based on sflow traffic accounting data from the peering LANs and route server BGP peerings.
    • This peering matrix only detects if there is bidirectional TCP flow between routers at . It cannot detect whether there are actually prefixes swapped between routers.