asn.dev

Observed topology

AS268538 Conecta Network Telecom LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268538: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv651
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267988VLMAX TELECOMUnclassifiedIPv4 IPv6162
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv439

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6181
AS267988VLMAX TELECOMUnclassifiedIPv4 IPv6162
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6135
AS28135ASSOCIACAO NACIONAL PARA INCLUSAO DIGITAL - ANIDUnclassifiedIPv4 IPv672
AS6939Hurricane Electric LLCTransitIPv632
AS266931RE Servicos de Comunicacao MultimidiaUnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64

Provenance

Where this comes from

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