asn.dev

Observed topology

AS6306 AS6306 - TELEFONICA VENEZOLANA, C.A.

Unclassified LACNIC NSP

Upstreams 4 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 0
Upstream graph Who carries AS6306, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS6306 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6306: 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.

ASNetworkTypeFamiliesPaths seen
AS19978CIRION TECHNOLOGIES ARGENTINA S.A.UnclassifiedIPv44,170
AS394684GOLD DATA USA INCUnclassifiedIPv42,986
AS23520Columbus Networks USA, Inc.ResidentialIPv4400
AS263703VIGINET C.AResidentialIPv4366

Transit

Downstream networks

inferred

Networks for which AS6306 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS269732WUIPI TECH CAUnclassifiedIPv4232
AS272864CIDATA, C.AUnclassifiedIPv4117
AS273010TECNOSYSTEM IO, C.AUnclassifiedIPv463
AS272955GRUPO TECNOLIFE, C.A.UnclassifiedIPv457
AS262176BANCO EXTERIORUnclassifiedIPv453
AS28089BANCO CENTRAL DE VENEZUELAUnclassifiedIPv414
AS274180SOFTELINET SOLUCIONES TECNOLOGICAS, C.A.UnclassifiedIPv41

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS6306 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS19978CIRION TECHNOLOGIES ARGENTINA S.A.UnclassifiedIPv44,226
AS394684GOLD DATA USA INCUnclassifiedIPv43,477
AS23520Columbus Networks USA, Inc.ResidentialIPv4400
AS263703VIGINET C.AResidentialIPv4366
AS269732WUIPI TECH CAUnclassifiedIPv4232
AS272864CIDATA, C.AUnclassifiedIPv4117
AS273010TECNOSYSTEM IO, C.AUnclassifiedIPv463
AS272955GRUPO TECNOLIFE, C.A.UnclassifiedIPv457
AS262176BANCO EXTERIORUnclassifiedIPv453
AS28089BANCO CENTRAL DE VENEZUELAUnclassifiedIPv414

All 11 adjacent →

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.