Observed topology

AS266394 SIGTEL SERVICOS DE TELECOMUNICACOES LTDA

Unclassified LACNIC

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266394: 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
AS265147	UP Fibra	Residential	IPv4 IPv6	308
AS52965	1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA	Unclassified	IPv4	159
AS6939	Hurricane Electric LLC	Transit	IPv6	68

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS275653	YOUFIBER TELECOMUNICACAO LTDA	Unclassified	IPv6	232
AS268526	Conect Virtua Provedor de Internet Banda Larga	Unclassified	IPv4 IPv6	49

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS265147	UP Fibra	Residential	IPv4 IPv6	724
AS275653	YOUFIBER TELECOMUNICACAO LTDA	Unclassified	IPv4 IPv6	378
AS52965	1TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDA	Unclassified	IPv4	159
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	79
AS268526	Conect Virtua Provedor de Internet Banda Larga	Unclassified	IPv4 IPv6	49

Provenance

Where this comes from

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