asn.dev

Observed topology

AS269589 MECONECTE COM

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS269589: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv653
AS3356Level 3 Parent, LLCTransitIPv4 IPv646
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv644
AS24482SG.GSHostingIPv61
AS37721Virtual Technologies & SolutionsResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266626Litoral TelecomUnclassifiedIPv4156
AS271445PORTO NET TELECOMUNICACOES LTDA-MEUnclassifiedIPv4156
AS262521pgf telecomunicacoes ltdaUnclassifiedIPv489
AS268837J CAVALCANTE DE LIMA INFORMATICA - LTDAUnclassifiedIPv659
AS267970MARLICO JOSE DA SILA INFORMATICA MEUnclassifiedIPv4 IPv638

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6457
AS266626Litoral TelecomUnclassifiedIPv4 IPv6352
AS61568ALOO TELECOM - FSF TECNOLOGIA SAResidentialIPv4 IPv6261
AS271445PORTO NET TELECOMUNICACOES LTDA-MEUnclassifiedIPv4156
AS262521pgf telecomunicacoes ltdaUnclassifiedIPv489
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS263276BBG TELECOM LTDAResidentialIPv659
AS268837J CAVALCANTE DE LIMA INFORMATICA - LTDAUnclassifiedIPv659
AS267970MARLICO JOSE DA SILA INFORMATICA MEUnclassifiedIPv4 IPv638
AS24482SG.GSHostingIPv61

Provenance

Where this comes from

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