-
bilat: 0, multilat: 0
-
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 TurkIX member is not listed on this peering matrix, it is because they are
currently not actively peering at TurkIX, 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 TurkIX peering
LANs and route server BGP peerings.
-
This peering matrix only detects if there is bidirectional TCP flow between routers at
TurkIX. It cannot detect whether there are actually prefixes swapped between routers.