asn.dev

Observed topology

AS262338 IKNET INTERNET KARIRI LTDA

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262338: 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
AS61680ACESSO SIMPLES LTDAResidentialIPv4 IPv6327
AS262832Infotechnet Informatica e Assistencia Tecnica LtdaResidentialIPv4 IPv6293
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6291
AS6939Hurricane Electric LLCTransitIPv6137
AS1031PEER 1031 LLCUnclassifiedIPv435
AS3303Swisscom (Schweiz) AGResidentialIPv47

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS61680ACESSO SIMPLES LTDAResidentialIPv4 IPv6327
AS262832Infotechnet Informatica e Assistencia Tecnica LtdaResidentialIPv4 IPv6293
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv6291
AS6939Hurricane Electric LLCTransitIPv6137
AS1031PEER 1031 LLCUnclassifiedIPv435
AS3303Swisscom (Schweiz) AGResidentialIPv47

Provenance

Where this comes from

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