asn.dev

Observed topology

AS274818 AS274818 - CONEXAO MAIS EMPRESA DE TELECOMUNICACOES LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274818: 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
AS262725RG SILVEIRA LTDAResidentialIPv4 IPv6302
AS269269V1 InformaticaUnclassifiedIPv488
AS264127EMITEL - Empresa de Informatica e Telecom. LTDAResidentialIPv4 IPv673

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv460
AS268077WEBLINK TECNOLOGIA LTDAUnclassifiedIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262725RG SILVEIRA LTDAResidentialIPv4 IPv6343
AS269269V1 InformaticaUnclassifiedIPv4 IPv6124
AS264127EMITEL - Empresa de Informatica e Telecom. LTDAResidentialIPv4 IPv692
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv460
AS268077WEBLINK TECNOLOGIA LTDAUnclassifiedIPv636

Provenance

Where this comes from

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