asn.dev

Observed topology

AS265187 STEEL WEB PROVEDORES DE ACESSO LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265187: 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
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv6240
AS6057Administracion Nacional de TelecomunicacionesResidentialIPv4 IPv6216
AS6939Hurricane Electric LLCTransitIPv6176
AS24482SG.GSHostingIPv610
AS37721Virtual Technologies & SolutionsResidentialIPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268790EASY NET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6476
AS266166GLOBALNET SERVICOS E INFORMATICA LTDA-MEResidentialIPv4 IPv621
AS270268FiberPon telecomUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS268790EASY NET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6476
AS6057Administracion Nacional de TelecomunicacionesResidentialIPv4 IPv6448
AS6939Hurricane Electric LLCTransitIPv4 IPv6445
AS53181Avanca Telecom e Servicos LTDAUnclassifiedIPv4 IPv6266
AS266166GLOBALNET SERVICOS E INFORMATICA LTDA-MEResidentialIPv4 IPv686
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv645
AS24482SG.GSHostingIPv4 IPv623
AS270268FiberPon telecomUnclassifiedIPv414

Provenance

Where this comes from

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