asn.dev

Observed topology

AS265268 AS265268 - Smart Solucoes Tecnologicas

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265268: 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
AS264420TurboNet TelecomUnclassifiedIPv4 IPv6250

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271168JJ DOS SANTOS SERVICO DE COMUNICACAO MEUnclassifiedIPv4 IPv6240
AS267143CM Net Servicos de Comunicacao Multimidia LTDAUnclassifiedIPv4 IPv6179
AS270334NET 100AUnclassifiedIPv4 IPv690
AS265432Opty Internet LtdaUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264420TurboNet TelecomUnclassifiedIPv4 IPv6791
AS271168JJ DOS SANTOS SERVICO DE COMUNICACAO MEUnclassifiedIPv4 IPv6240
AS267143CM Net Servicos de Comunicacao Multimidia LTDAUnclassifiedIPv4 IPv6179
AS270334NET 100AUnclassifiedIPv4 IPv690
AS265432Opty Internet LtdaUnclassifiedIPv632

Provenance

Where this comes from

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