Observed topology

AS268071 AS268071 - GRUPO TDKOM

Unclassified LACNIC Cable/DSL/ISP

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

Upstream graph Who carries AS268071, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS268071 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268071: 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.

AS	Network	Type	Families	Paths seen
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	131
AS265330	Ponto a Ponto Telecomunicacoes	Unclassified	IPv4	60
AS52695	NETFACIL LTDA ME	Unclassified	IPv4	52
AS264144	ASAP GLOBAL TELECOM	Unclassified	IPv4 IPv6	29
AS263478	DUFIBRANET TELECOM LTDA	Residential	IPv4	9
AS270548	AGI TELECOM LTDA	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS271253	LINK BRASIL TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	131
AS265330	Ponto a Ponto Telecomunicacoes	Unclassified	IPv4	60
AS52695	NETFACIL LTDA ME	Unclassified	IPv4	52
AS264144	ASAP GLOBAL TELECOM	Unclassified	IPv4 IPv6	29
AS263478	DUFIBRANET TELECOM LTDA	Residential	IPv4	9
AS270548	AGI TELECOM LTDA	Unclassified	IPv4	1

Provenance

Where this comes from

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