Adjacent networks
AS133613 MTEL-AS MTel telecommunication company ltd.
Residential APNIC
Adjacency
Adjacent networks
Every AS seen directly next to AS133613 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,061 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,332 |
| AS134550 | Centro de Informacoes Tecnologia de Macau | Unclassified | IPv4 | 634 |
| AS136793 | MACAU COMMUNICATION NETWORKS COMPANY LIMITED | Unclassified | IPv4 IPv6 | 478 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | Unclassified | IPv4 IPv6 | 137 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 136 |
| AS400696 | MIBURA, INC. | Unclassified | IPv4 IPv6 | 100 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 79 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 68 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 14 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 3 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 3 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 3 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 3 |
| AS48185 | team.blue NV | Unclassified | IPv4 | 3 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 | 3 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 | 3 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 3 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 2 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 2 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 2 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 1 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 1 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 1 |
Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.