asn.dev

Observed topology

AS52777 BR27 Servicos de Tecnologia Ltda.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52777: 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
AS271508OPIX SERVICOS DE TECNOLOGIA EIRELIUnclassifiedIPv4 IPv680
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv453
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv632
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv4 IPv6423
AS61735RIX INTERNET LTDAUnclassifiedIPv428

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv4 IPv6423
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6362
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4167
AS271508OPIX SERVICOS DE TECNOLOGIA EIRELIUnclassifiedIPv4 IPv681
AS61735RIX INTERNET LTDAUnclassifiedIPv428
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv67

Provenance

Where this comes from

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