Observed topology

AS266388 AS266388 - ZAZ NATAL

Residential APNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266388: 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
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4 IPv6	162
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	153
AS28598	DB3 SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv4	21
AS266460	NetGo Telecomunicacoes do Brasil	Residential	IPv6	7
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS262872	DIGICONTROL SERVICOS DE PROVEDORES LTDA	Residential	IPv4 IPv6	151

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS16735	ALGAR TELECOM S/A	Unclassified	IPv4 IPv6	162
AS10429	TELEFONICA BRASIL S.A	Residential	IPv4 IPv6	157
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	153
AS262872	DIGICONTROL SERVICOS DE PROVEDORES LTDA	Residential	IPv4 IPv6	151
AS28598	DB3 SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv4	21
AS266460	NetGo Telecomunicacoes do Brasil	Residential	IPv6	7

Provenance

Where this comes from

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