asn.dev

Observed topology

AS268732 AS268732 - CONECTA SERVICO DE COMUNICACAO MULTIMIDIA LTDA

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268732: 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
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv6243
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv69
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262767Avelino e Rodrigues LTDAUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS269096N&K TECNOLOGIA LTDAUnclassifiedIPv4 IPv6257
AS262767Avelino e Rodrigues LTDAUnclassifiedIPv4 IPv694
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv658
AS268696Tuddo Telecom Ltda.UnclassifiedIPv4 IPv657
AS24482SG.GSHostingIPv4 IPv611
AS35280F5 Networks SARLHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67

Provenance

Where this comes from

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