asn.dev

Observed topology

AS268509 COMPLETA Telecomunicacoes Ltda

Unclassified LACNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268509: 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
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv4 IPv6149
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS24482SG.GSHostingIPv4 IPv610
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS35280F5 Networks SARLHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271758Access World Services LTDAUnclassifiedIPv4 IPv6353

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS271758Access World Services LTDAUnclassifiedIPv4 IPv6353
AS28189JR & JS ENGENHARIA E COMERCIO LTDAUnclassifiedIPv4 IPv6305
AS264144ASAP GLOBAL TELECOMUnclassifiedIPv4 IPv6206
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

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