asn.dev

Observed topology

AS268665 TEONET TELECOMUNICACOES LTDA

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268665: 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
AS2914NTT America, Inc.TransitIPv4 IPv692
AS264127EMITEL - Empresa de Informatica e Telecom. LTDAResidentialIPv4 IPv661
AS6939Hurricane Electric LLCTransitIPv441
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv65
AS262725RG SILVEIRA LTDAResidentialIPv42

Transit

Downstream networks

inferred

Networks for which AS268665 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 AS268665 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv692
AS264127EMITEL - Empresa de Informatica e Telecom. LTDAResidentialIPv4 IPv661
AS6939Hurricane Electric LLCTransitIPv441
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv65
AS35280F5 Networks SARLHostingIPv4 IPv65
AS262725RG SILVEIRA LTDAResidentialIPv42

Provenance

Where this comes from

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