Observed topology

AS266029 AS266029 - SBNET TELECOM

Residential ARIN

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266029: 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
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	224
AS6939	Hurricane Electric LLC	Transit	IPv4	62
AS28146	MHNET TELECOM	Residential	IPv4 IPv6	44
AS24482	SG.GS	Hosting	IPv4 IPv6	8
AS35280	F5 Networks SARL	Hosting	IPv4	4
AS37721	Virtual Technologies & Solutions	Residential	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS267952	HILINK TECNOLOGIA E COMUNICACAO LTDA	Unclassified	IPv4	59
AS272218	Luiz Henrique Rocha Maciel	Unclassified	IPv6	36

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS53062	GGNET TELECOMUNICACOES LTDA	Unclassified	IPv4 IPv6	306
AS6939	Hurricane Electric LLC	Transit	IPv4	73
AS267952	HILINK TECNOLOGIA E COMUNICACAO LTDA	Unclassified	IPv4	59
AS28146	MHNET TELECOM	Residential	IPv4 IPv6	44
AS272218	Luiz Henrique Rocha Maciel	Unclassified	IPv6	36
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS35280	F5 Networks SARL	Hosting	IPv4	4
AS37721	Virtual Technologies & Solutions	Residential	IPv4	4

Provenance

Where this comes from

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