Peering Matrix Peering LAN #1
1 1 2 |
6 8 2 3 |
8 0 7 5 |
1 5 1 6 9 |
4 4 9 0 1 |
4 7 2 8 8 |
5 7 1 5 2 |
2 0 4 4 5 7 |
2 0 6 1 6 3 |
2 0 8 9 7 2 |
2 1 3 6 4 0 |
2 1 6 1 4 5 |
||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AS112 Reverse DNS | 112 | ||||||||||||
3C1B Telekom | 6823 | ||||||||||||
Microsoft | 8075 | ||||||||||||
Google LLC | 15169 | ||||||||||||
BelCloud Ltd. | 44901 | ||||||||||||
FIXNET TELEKOM LTD. STI. | 47288 | ||||||||||||
Teknet Veri Merkezi | 57152 | ||||||||||||
Atlantis Telekomünikasyon bil. hizm. san.tic.ltd.şti. | 204457 | ||||||||||||
TBTNET | 206163 | ||||||||||||
GIBIRNET | 208972 | ||||||||||||
Talido LTD | 213640 | ||||||||||||
7DC INTERNET LTD. | 216145 |
- bilat: 0, multilat: 66
- 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 IXP member is not listed on this peering matrix, it is because they are currently not actively peering at IXP, 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 IXP peering LANs and route server BGP peerings.
- This peering matrix only detects if there is bidirectional TCP flow between routers at IXP. It cannot detect whether there are actually prefixes swapped between routers.