asn.dev

Observed topology

AS52877 TUPIX INTERNET EXCHANGE

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52877: 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
AS264138LMS - LAST MILE SERVICES LTDAUnclassifiedIPv4420
AS263080GTi TELECOMUNICACOES S/AUnclassifiedIPv460
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv460
AS3356Level 3 Parent, LLCTransitIPv634
AS6939Hurricane Electric LLCTransitIPv618
AS24482SG.GSHostingIPv61
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263108OPANET TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6339
AS266592REAL LIFE COMERCIO E SERVICOS LTDAResidentialIPv4176
AS264295Unolink Telecom LtdaUnclassifiedIPv4 IPv6174

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS263080GTi TELECOMUNICACOES S/AUnclassifiedIPv4732
AS264138LMS - LAST MILE SERVICES LTDAUnclassifiedIPv4420
AS263108OPANET TELECOMUNICACOES LTDA - MEUnclassifiedIPv4 IPv6339
AS266592REAL LIFE COMERCIO E SERVICOS LTDAResidentialIPv4234
AS264295Unolink Telecom LtdaUnclassifiedIPv4 IPv6174
AS3356Level 3 Parent, LLCTransitIPv6109
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv618
AS24482SG.GSHostingIPv61
AS35280F5 Networks SARLHostingIPv61

All 11 adjacent →

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.