asn.dev

Observed topology

AS269360 AS269360 - Internet Tecnologia Ltda

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269360: 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
AS263903INFORBARRA TELECOMUnclassifiedIPv4 IPv6350
AS6939Hurricane Electric LLCTransitIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270359iXnet FibraUnclassifiedIPv4 IPv6202
AS28188Pronto Net Ltda.UnclassifiedIPv460
AS270910MULTI SUPORTE TELECOMUNICACOES LTDA - MEUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263903INFORBARRA TELECOMUnclassifiedIPv4 IPv6630
AS270359iXnet FibraUnclassifiedIPv4 IPv6202
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS28188Pronto Net Ltda.UnclassifiedIPv460
AS270910MULTI SUPORTE TELECOMUNICACOES LTDA - MEUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv62
AS35280F5 Networks SARLHostingIPv61

Provenance

Where this comes from

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