Observed topology
AS21826 Corporacion Telemic C.A.
Unclassified LACNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS21826: 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 |
|---|---|---|---|---|
| AS23520 | Columbus Networks USA, Inc. | Residential | IPv4 IPv6 | 30,479 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 8,422 |
| AS52320 | GlobeNet Cabos Submarinos Colombia, S.A.S. | Unclassified | IPv4 IPv6 | 6,978 |
| AS39838 | Valor Information Technologies, S.L. | Unclassified | IPv4 IPv6 | 1,456 |
| AS263703 | VIGINET C.A | Residential | IPv4 | 129 |
Transit
Downstream networks
Networks for which AS21826 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS272809 | THUNDERNET, C.A. | Residential | IPv4 IPv6 | 10,547 |
| AS263806 | GALAXY ENTERTAINMENT DE VENEZUELA, S.C.A. | Unclassified | IPv4 IPv6 | 1,284 |
| AS269946 | BOOM SOLUTIONS C.A. | Unclassified | IPv4 IPv6 | 1,076 |
| AS269820 | FULL DATA COMUNICACIONES C.A. | Unclassified | IPv4 IPv6 | 1,049 |
| AS273155 | DATANET VZLA 2021, C.A | Unclassified | IPv4 IPv6 | 960 |
| AS269750 | Gandalf Comunicaciones C.A. | Unclassified | IPv4 | 812 |
| AS266841 | GALANET SOLUTION C.A. | Unclassified | IPv4 | 522 |
| AS271812 | CONEXT VENEZUELA, C.A. | Unclassified | IPv4 IPv6 | 450 |
| AS271909 | TELECOMUNICACIONES, MANTENIMIENTO Y SERVICIOS P&C, C.A. | Unclassified | IPv4 | 423 |
| AS270026 | RED SERVITEL, CA | Unclassified | IPv4 | 406 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21826 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS23520 | Columbus Networks USA, Inc. | Residential | IPv4 IPv6 | 39,450 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 20,650 |
| AS272809 | THUNDERNET, C.A. | Residential | IPv4 IPv6 | 10,547 |
| AS52320 | GlobeNet Cabos Submarinos Colombia, S.A.S. | Unclassified | IPv4 IPv6 | 7,044 |
| AS269946 | BOOM SOLUTIONS C.A. | Unclassified | IPv4 IPv6 | 1,886 |
| AS39838 | Valor Information Technologies, S.L. | Unclassified | IPv4 IPv6 | 1,456 |
| AS263806 | GALAXY ENTERTAINMENT DE VENEZUELA, S.C.A. | Unclassified | IPv4 IPv6 | 1,284 |
| AS269820 | FULL DATA COMUNICACIONES C.A. | Unclassified | IPv4 IPv6 | 1,055 |
| AS273155 | DATANET VZLA 2021, C.A | Unclassified | IPv4 IPv6 | 960 |
| AS269750 | Gandalf Comunicaciones C.A. | Unclassified | IPv4 | 812 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.