Peering Matrix VLAN100-PEERING-IPv4
4 2 |
1 1 2 |
3 8 5 6 |
6 3 0 6 |
1 1 5 6 2 |
2 1 8 2 6 |
2 5 1 5 2 |
2 7 7 1 7 |
5 2 2 2 4 |
1 9 7 0 0 0 |
2 6 9 8 3 2 |
||
---|---|---|---|---|---|---|---|---|---|---|---|---|
PCH AS42 | 42 | |||||||||||
DNS-OARC-112 | 112 | |||||||||||
PCH AS3856 | 3856 | |||||||||||
Telefonica Venezolana C.A. | 6306 | |||||||||||
NETUNO | 11562 | |||||||||||
CorporaciĆ³n Telemic Network | 21826 | |||||||||||
RIPE NCC K-Root Operations | 25152 | |||||||||||
Corporacion Digitel | 27717 | |||||||||||
LACNIC - Latin American and Caribbean IP address | 52224 | |||||||||||
RIPE NCC Authoritative DNS | 197000 | |||||||||||
MDSTELECOM | 269832 |
- bilat: 0, multilat: 55
- 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 NAP VE member is not listed on this peering matrix, it is because they are currently not actively peering at NAP VE, 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 NAP VE peering LANs and route server BGP peerings.
- This peering matrix only detects if there is bidirectional TCP flow between routers at NAP VE. It cannot detect whether there are actually prefixes swapped between routers.