Observed topology
AS269822 AS269822 - COLOMBIA MAS TV S.A.S
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS269822: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 683 |
| AS18678 | INTERNEXA S.A. E.S.P | Unclassified | IPv4 IPv6 | 475 |
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 366 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 121 |
| AS262191 | LIBERTY NETWORKS DE COLOMBIA S.A.S | Unclassified | IPv4 | 15 |
| AS27951 | Media Commerce Partners S.A | Residential | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS269822 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS270046 | FEDERACION COLOMBIANA DE MUNICIPIOS | Unclassified | IPv6 | 33 |
Adjacency
Adjacent networks
Every AS seen directly next to AS269822 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 683 |
| AS18678 | INTERNEXA S.A. E.S.P | Unclassified | IPv4 IPv6 | 475 |
| AS52468 | UFINET PANAMA S.A. | Unclassified | IPv4 IPv6 | 399 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 121 |
| AS270046 | FEDERACION COLOMBIANA DE MUNICIPIOS | Unclassified | IPv6 | 33 |
| AS262191 | LIBERTY NETWORKS DE COLOMBIA S.A.S | Unclassified | IPv4 | 15 |
| AS27951 | Media Commerce Partners S.A | Residential | IPv6 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.