asn.dev

Observed topology

AS262557 VIA SUL TELECOMUNICACOES LTDA ME

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262557: 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
AS28173Dinamica Telecomunicacoes LtdaUnclassifiedIPv4 IPv6211
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6203
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267159LTNET Telecomunicacoes EIRELE MEUnclassifiedIPv4 IPv6423
AS275619Apoio Digital TiUnclassifiedIPv4 IPv6146

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv6573
AS267159LTNET Telecomunicacoes EIRELE MEUnclassifiedIPv4 IPv6424
AS6939Hurricane Electric LLCTransitIPv4 IPv6332
AS28173Dinamica Telecomunicacoes LtdaUnclassifiedIPv4 IPv6253
AS275619Apoio Digital TiUnclassifiedIPv4 IPv6146
AS35280F5 Networks SARLHostingIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv66

Provenance

Where this comes from

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