asn.dev

Observed topology

AS267638 AS267638 - Wind Telecomunicacao do Brasil Ltda - ME

Hosting LACNIC Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267638: 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
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6289
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS1031PEER 1031 LLCUnclassifiedIPv411
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS24482SG.GSHostingIPv4 IPv64
AS33891Core-Backbone GmbHHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268275GOOD TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4427
AS270509Turbinado Telecom Ltda - MEUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS11432Telium Telecomunicacoes LtdaHostingIPv4 IPv6720
AS268275GOOD TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4427
AS1031PEER 1031 LLCUnclassifiedIPv491
AS6939Hurricane Electric LLCTransitIPv4 IPv677
AS270509Turbinado Telecom Ltda - MEUnclassifiedIPv461
AS3303Swisscom (Schweiz) AGResidentialIPv418
AS24482SG.GSHostingIPv4 IPv612
AS33891Core-Backbone GmbHHostingIPv49

Provenance

Where this comes from

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