Observed topology
AS269832 AS269832 - MDS TELECOM C.A.
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS269832: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 233 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 170 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 129 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 124 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 72 |
| AS12956 | TELEFONICA GLOBAL SOLUTIONS SL | Transit | IPv4 | 47 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS269832 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS27889 | Telecomunicaciones MOVILNET | Unclassified | IPv4 IPv6 | 1,997 |
| AS272018 | KM TECHNOLOGY, C.A. | Unclassified | IPv4 IPv6 | 416 |
| AS273890 | SERVICIOS NAP VEN, C.A. | Unclassified | IPv4 IPv6 | 358 |
| AS274314 | TUYEROS NETWORKS C.A | Unclassified | IPv4 IPv6 | 357 |
| AS273173 | TELECOM 3 C.A | Unclassified | IPv4 IPv6 | 283 |
| AS273893 | COSAN TELECOM C.A. | Unclassified | IPv4 IPv6 | 178 |
| AS275004 | LUE17 | Unclassified | IPv4 IPv6 | 150 |
| AS267722 | INTERSPEED C.A. | Unclassified | IPv4 | 118 |
| AS274180 | SOFTELINET SOLUCIONES TECNOLOGICAS, C.A. | Unclassified | IPv4 | 94 |
| AS273058 | SOLUCIONES TECNICAS R.V.A C.A | Unclassified | IPv4 | 32 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269832 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS27889 | Telecomunicaciones MOVILNET | Unclassified | IPv4 IPv6 | 1,997 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,614 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,014 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 814 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 752 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 518 |
| AS272018 | KM TECHNOLOGY, C.A. | Unclassified | IPv4 IPv6 | 416 |
| AS273890 | SERVICIOS NAP VEN, C.A. | Unclassified | IPv4 IPv6 | 358 |
| AS274314 | TUYEROS NETWORKS C.A | Unclassified | IPv4 IPv6 | 357 |
| AS273173 | TELECOM 3 C.A | Unclassified | IPv4 IPv6 | 283 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. 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.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.