asn.dev

Observed topology

AS274384 AS274384 - VELIZ INTERNET E SERVICOS LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS274384: 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
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv630

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271456NET2YOU NETWORK LTDAUnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271456NET2YOU NETWORK LTDAUnclassifiedIPv4 IPv692
AS270814ZAAZ PROVEDOR DE INTERNET E TELECOMUNICACOES LTDAResidentialIPv655
AS270585Fly Conecta Internet LTDAUnclassifiedIPv4 IPv650
AS273363YASMIN ARUAM DOS SANTOS FERREIRA DE MORAESResidentialIPv4 IPv617

Provenance

Where this comes from

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