Observed topology

AS262594 AS262594 - 4iNET Communications

Unclassified LACNIC

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262594: 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
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	917

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS269603	lynn telecom	Unclassified	IPv4 IPv6	470
AS53245	ActiON Infinite Communications, Brazil.	Unclassified	IPv4	174
AS269677	Gerson Cerqueira	Unclassified	IPv4 IPv6	152
AS266046	INTERCONNECT TRANSMISSAO DE DADOS	Unclassified	IPv4	118
AS268117	RAFAEL FERNANDES DE MEDEIROS	Unclassified	IPv4	85
AS61823	SPINT PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS268624	Gamers Club Ltda	Unclassified	IPv4 IPv6	1,974
AS269603	lynn telecom	Unclassified	IPv4 IPv6	470
AS53245	ActiON Infinite Communications, Brazil.	Unclassified	IPv4	174
AS269677	Gerson Cerqueira	Unclassified	IPv4 IPv6	152
AS266046	INTERCONNECT TRANSMISSAO DE DADOS	Unclassified	IPv4	118
AS268117	RAFAEL FERNANDES DE MEDEIROS	Unclassified	IPv4	85
AS61823	SPINT PROVEDOR DE INTERNET LTDA	Unclassified	IPv4	58

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.