Observed topology

AS263606 AS263606 - COREIT - DATACENTER, SERV GER E INFRA TI LTDA

Unclassified LACNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263606: 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
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4 IPv6	113
AS270820	COMPUNET DO BRASIL TELECOM LTDA	Residential	IPv4	61
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	52
AS270551	CORELINK CONECT SEG E TRANSP DE DADOS LTDA	Unclassified	IPv4	14
AS28368	unnamed	Residential	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS270551	CORELINK CONECT SEG E TRANSP DE DADOS LTDA	Unclassified	IPv4	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4 IPv6	121
AS270820	COMPUNET DO BRASIL TELECOM LTDA	Residential	IPv4	61
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	52
AS263665	TECNET PROVEDOR DE ACESSO AS REDES DE COM. LTDA	Unclassified	IPv4	38
AS267460	unnamed	Unclassified	IPv4	38
AS270551	CORELINK CONECT SEG E TRANSP DE DADOS LTDA	Unclassified	IPv4	22
AS28368	unnamed	Residential	IPv4	2

Provenance

Where this comes from

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