asn.dev

Observed topology

AS269820 AS269820 - FULL DATA COMUNICACIONES C.A.

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269820: 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
AS263703VIGINET C.AResidentialIPv4 IPv61,816
AS21826Corporacion Telemic C.A.UnclassifiedIPv4 IPv61,072
AS10293CANTV Servicios, VenezuelaUnclassifiedIPv4575
AS394684GOLD DATA USA INCUnclassifiedIPv4 IPv6147

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2719514 EVER PLUG,C.A.ResidentialIPv4 IPv6396
AS274203LINK NETWORK, CA.UnclassifiedIPv664

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263703VIGINET C.AResidentialIPv4 IPv62,267
AS21826Corporacion Telemic C.A.UnclassifiedIPv4 IPv61,076
AS10293CANTV Servicios, VenezuelaUnclassifiedIPv4575
AS2719514 EVER PLUG,C.A.ResidentialIPv4 IPv6455
AS394684GOLD DATA USA INCUnclassifiedIPv4 IPv6211
AS274203LINK NETWORK, CA.UnclassifiedIPv664

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.