Peering Matrix Peering.263
|
1 4 2 3 0 |
2 2 3 5 9 |
3 6 5 2 7 |
6 5 0 0 0 |
6 5 0 0 1 |
3 9 4 1 4 0 |
3 9 8 0 1 3 |
||
|---|---|---|---|---|---|---|---|---|
| ark data centers LLC | 14230 | |||||||
| NETSKRTSYSTEMS-UK | 22359 | |||||||
| Rincon Wireless | 36527 | |||||||
| Involta-DEV | 65000 | |||||||
| ACME | 65001 | |||||||
| Native Network | 394140 | |||||||
| NGX Networks | 398013 |
- bilat: 0, multilat: 21
- 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 Tucson Internet Exchange member is not listed on this peering matrix, it is because they are currently not actively peering at Tucson Internet Exchange, 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 Tucson Internet Exchange peering LANs and route server BGP peerings.
- This peering matrix only detects if there is bidirectional TCP flow between routers at Tucson Internet Exchange. It cannot detect whether there are actually prefixes swapped between routers.