asn.dev

Observed topology

AS20255 Tecnowind S.A.

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20255: 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
AS3549Level 3 Parent, LLCTransitIPv4 IPv63,730
AS3356Level 3 Parent, LLCTransitIPv42,518

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273002TRACTORAL SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6249
AS52241Lunamen S.A.UnclassifiedIPv4190
AS52366Lunamen S.A.UnclassifiedIPv4180
AS273004MONTE CABLEVIDEO S AUnclassifiedIPv4 IPv6171
AS273012RISELCO SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6168
AS274302Tecnowind S.A.UnclassifiedIPv466
AS274201PARQUE DE LAS CIENCIAS S.A.UnclassifiedIPv460
AS61442PASWER INTERNATIONAL S.A.UnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3549Level 3 Parent, LLCTransitIPv4 IPv64,485
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,906
AS273002TRACTORAL SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6249
AS52241Lunamen S.A.UnclassifiedIPv4190
AS52366Lunamen S.A.UnclassifiedIPv4180
AS273004MONTE CABLEVIDEO S AUnclassifiedIPv4 IPv6171
AS273012RISELCO SOCIEDAD ANONIMAUnclassifiedIPv4 IPv6168
AS274302Tecnowind S.A.UnclassifiedIPv466
AS274201PARQUE DE LAS CIENCIAS S.A.UnclassifiedIPv460
AS61442PASWER INTERNATIONAL S.A.UnclassifiedIPv459

Provenance

Where this comes from

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