asn.dev

Observed topology

AS274642 AS274642 - TELECOMUNICACOES BRASILIA LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274642: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6110
AS61884OLLA COMUNICACAO LTDAUnclassifiedIPv4 IPv696
AS266167CELERIX TECNOLOGIA DE TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv691
AS4230CLARO S.A.ResidentialIPv664
AS264112CAMON PROVEDORUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv630
AS24482SG.GSHostingIPv61
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268473LinkSul internetUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264112CAMON PROVEDORUnclassifiedIPv4120
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6110
AS61884OLLA COMUNICACAO LTDAUnclassifiedIPv4 IPv696
AS266167CELERIX TECNOLOGIA DE TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv691
AS4230CLARO S.A.ResidentialIPv664
AS268473LinkSul internetUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv630
AS24482SG.GSHostingIPv61
AS35280F5 Networks SARLHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

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.