asn.dev

Observed topology

AS271291 CONECT SOLUCTION LTDA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS271291: 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
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv6201
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv4134
AS269194ST1 INTERNETResidentialIPv4 IPv6130

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271612LOGO TelecomUnclassifiedIPv4 IPv6103
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv663
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv612
AS271148NEXTALL TELECOMUNICACOES EMPREENDIMENTOS LTDAUnclassifiedIPv4 IPv610
AS264974TELECOM SCAE LTDAUnclassifiedIPv66
AS271651D P DOS SANTOS SERVICOS DE INTERNETUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269194ST1 INTERNETResidentialIPv4 IPv6258
AS265269MEGA TELE INFORMATICAUnclassifiedIPv4 IPv6237
AS269558B S V TELECOMUNICACOES E SERVICOS LTDAResidentialIPv4 IPv6168
AS271612LOGO TelecomUnclassifiedIPv4 IPv6103
AS271493SPEED NET PEDRAUnclassifiedIPv4 IPv663
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv612
AS271148NEXTALL TELECOMUNICACOES EMPREENDIMENTOS LTDAUnclassifiedIPv4 IPv610
AS264974TELECOM SCAE LTDAUnclassifiedIPv66
AS271651D P DOS SANTOS SERVICOS DE INTERNETUnclassifiedIPv4 IPv64

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.