asn.dev

Observed topology

AS267450 oliveira & sousa comunicacoes Ltda

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267450: 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
AS262355VSX NetworksUnclassifiedIPv4 IPv6268
AS6939Hurricane Electric LLCTransitIPv4 IPv673
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv68
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2635381TOC INFORMATICA LTDAUnclassifiedIPv4351
AS270893JAGUARNET TELECOMUNICACAO LTDAUnclassifiedIPv426

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS262355VSX NetworksUnclassifiedIPv4 IPv6563
AS2635381TOC INFORMATICA LTDAUnclassifiedIPv4351
AS6939Hurricane Electric LLCTransitIPv4 IPv697
AS53115ISPX Solucoes em Telecomunicacoes SPE LtdaUnclassifiedIPv4 IPv688
AS270893JAGUARNET TELECOMUNICACAO LTDAUnclassifiedIPv426
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv611
AS1031PEER 1031 LLCUnclassifiedIPv42

Provenance

Where this comes from

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