asn.dev

Observed topology

AS61704 Conectiva Telecom LTDA

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61704: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6228
AS268311Dconnect TelecomResidentialIPv4192
AS6939Hurricane Electric LLCTransitIPv4 IPv6159
AS24482SG.GSHostingIPv4 IPv611
AS35280F5 Networks SARLHostingIPv64
AS37721Virtual Technologies & SolutionsResidentialIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270341Futel TelecomResidentialIPv4 IPv6144
AS271707TRANSNETWORK TELECOMUNICACOESUnclassifiedIPv4 IPv675
AS271478Interlink Solucoes Em Telecomunicacoes Ltda - MEResidentialIPv4 IPv62

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6436
AS268311Dconnect TelecomResidentialIPv4194
AS6939Hurricane Electric LLCTransitIPv4 IPv6159
AS270341Futel TelecomResidentialIPv4 IPv6144
AS271707TRANSNETWORK TELECOMUNICACOESUnclassifiedIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv626
AS35280F5 Networks SARLHostingIPv64
AS37721Virtual Technologies & SolutionsResidentialIPv64
AS271478Interlink Solucoes Em Telecomunicacoes Ltda - MEResidentialIPv4 IPv62

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.