Observed topology

AS266072 GLOBAL TELECOMUNICACOES EIRELI - ME

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266072: 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
AS263629	ALLREDE TELECOM MT / BRASIL TECPAR	Unclassified	IPv4 IPv6	140
AS266214	UTIL PROVEDOR DE INTERNET LTDA - ME	Unclassified	IPv4	77
AS2266072	unnamed	Unclassified	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52757	Sorriso Internet Ltda.	Unclassified	IPv4 IPv6	158
AS270457	INACIO MIGUEL SCHERER	Unclassified	IPv4 IPv6	94
AS267059	NETVIP MT	Residential	IPv4	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS266214	UTIL PROVEDOR DE INTERNET LTDA - ME	Unclassified	IPv4 IPv6	369
AS263629	ALLREDE TELECOM MT / BRASIL TECPAR	Unclassified	IPv4 IPv6	250
AS270457	INACIO MIGUEL SCHERER	Unclassified	IPv4 IPv6	178
AS52757	Sorriso Internet Ltda.	Unclassified	IPv4 IPv6	158
AS267059	NETVIP MT	Residential	IPv4	63
AS26607	KYNDRYL BRASIL SERVICOS LTDA	Unclassified	IPv4	3
AS2266072	unnamed	Unclassified	IPv4	3

Provenance

Where this comes from

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