asn.dev

Observed topology

AS269688 ITATIAIA INFORMATICA E TELECOMUNICACOES LTDA ME

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269688: 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
AS263623GOX S.A.HostingIPv4 IPv6175
AS28198SEMPRE TELECOMUNICACOES LTDAResidentialIPv4 IPv6102
AS6939Hurricane Electric LLCTransitIPv4 IPv654
AS52468UFINET PANAMA S.A.UnclassifiedIPv47
AS24482SG.GSHostingIPv4 IPv64
AS273478Sage NetworksUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264421BrumaNet TelecomUnclassifiedIPv4 IPv658

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263623GOX S.A.HostingIPv4 IPv6175
AS28198SEMPRE TELECOMUNICACOES LTDAResidentialIPv4 IPv6103
AS6939Hurricane Electric LLCTransitIPv4 IPv678
AS264421BrumaNet TelecomUnclassifiedIPv4 IPv658
AS3356Level 3 Parent, LLCTransitIPv4 IPv630
AS52468UFINET PANAMA S.A.UnclassifiedIPv47
AS24482SG.GSHostingIPv4 IPv66
AS273478Sage NetworksUnclassifiedIPv63
AS37721Virtual Technologies & SolutionsResidentialIPv61

Provenance

Where this comes from

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