asn.dev

Observed topology

AS28137 AS28137 - Vialink Solucoes de Tecnologia Ltda

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28137: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4440
AS6939Hurricane Electric LLCTransitIPv4 IPv6118
AS266166GLOBALNET SERVICOS E INFORMATICA LTDA-MEResidentialIPv459
AS263946RINGLINK TELECOM LTDAUnclassifiedIPv445
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263946RINGLINK TELECOM LTDAUnclassifiedIPv490

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4476
AS6939Hurricane Electric LLCTransitIPv4 IPv6172
AS263946RINGLINK TELECOM LTDAUnclassifiedIPv4135
AS266166GLOBALNET SERVICOS E INFORMATICA LTDA-MEResidentialIPv459
AS35280F5 Networks SARLHostingIPv61

Provenance

Where this comes from

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