asn.dev

Observed topology

AS53061 AS53061 - G2NET SUL PROVEDOR LTDA

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53061: 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
AS11432Telium Telecomunicacoes LtdaHostingIPv4123
AS275716Vertix Tecnologia Solucoes em CloudUnclassifiedIPv4120
AS266201VERO S.AResidentialIPv484
AS8167V talResidentialIPv4 IPv670
AS28146MHNET TELECOMResidentialIPv4 IPv663
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264490ANDRA TELECOMUnclassifiedIPv4 IPv6243
AS275716Vertix Tecnologia Solucoes em CloudUnclassifiedIPv69

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264490ANDRA TELECOMUnclassifiedIPv4 IPv6716
AS8167V talResidentialIPv4 IPv6534
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6323
AS275716Vertix Tecnologia Solucoes em CloudUnclassifiedIPv4 IPv6141
AS266201VERO S.AResidentialIPv4 IPv6129
AS28146MHNET TELECOMResidentialIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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