asn.dev

Observed topology

AS61786 E. D. SERVICOS DE COMUNICACOES LTDA

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61786: 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
AS53087TELY Ltda.ResidentialIPv4282
AS271231J. S. dos Santos Junior Comunicacoes MEUnclassifiedIPv4248
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6234
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6108
AS6939Hurricane Electric LLCTransitIPv429
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271231J. S. dos Santos Junior Comunicacoes MEUnclassifiedIPv4 IPv6475

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271231J. S. dos Santos Junior Comunicacoes MEUnclassifiedIPv4 IPv6723
AS53087TELY Ltda.ResidentialIPv4468
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6355
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6306
AS6939Hurricane Electric LLCTransitIPv4 IPv668
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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