asn.dev

Observed topology

AS61871 AS61871 - SiqueiraLink Internet Banda Larga

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61871: 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
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6273
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6163
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4147
AS6939Hurricane Electric LLCTransitIPv634
AS24482SG.GSHostingIPv4 IPv611
AS28368unnamedResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263882PROVEDOR MTEC LTDAUnclassifiedIPv4 IPv6279
AS268312PROREDES INTERNET SERVICOS DE INFORMATICA LTDA - MUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6409
AS263882PROVEDOR MTEC LTDAUnclassifiedIPv4 IPv6279
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6258
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv6251
AS268312PROREDES INTERNET SERVICOS DE INFORMATICA LTDA - MUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv634
AS24482SG.GSHostingIPv4 IPv614
AS28368unnamedResidentialIPv43

Provenance

Where this comes from

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