asn.dev

Observed topology

AS61751 SINTNET-TELECOMUNICACOES E INFORMATICA LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61751: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6279
AS3356Level 3 Parent, LLCTransitIPv4 IPv6187
AS267470CX ProResidentialIPv4 IPv6152
AS35280F5 Networks SARLHostingIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS263009FORTE TELECOM LTDA.HostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271681R RODRIGUES MENEZES SERVICOS DE INTERNET LTDA MEUnclassifiedIPv4 IPv6311
AS269076L DA COSTA SILVA COMUNICACOESResidentialIPv4 IPv6279

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6539
AS6939Hurricane Electric LLCTransitIPv4 IPv6480
AS271681R RODRIGUES MENEZES SERVICOS DE INTERNET LTDA MEUnclassifiedIPv4 IPv6311
AS269076L DA COSTA SILVA COMUNICACOESResidentialIPv4 IPv6279
AS267470CX ProResidentialIPv4 IPv6152
AS24482SG.GSHostingIPv4 IPv621
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv621
AS35280F5 Networks SARLHostingIPv4 IPv618
AS263009FORTE TELECOM LTDA.HostingIPv4 IPv69

Provenance

Where this comes from

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