Observed topology

AS262590 AS262590 - NET ON LINE LTDA

Unclassified LACNIC NSP

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262590: 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
AS270403	LOCAL TELECOM LTDA	Unclassified	IPv4 IPv6	376
AS273440	JMT TELECOM - C DE SOUSA BEZERRA	Unclassified	IPv4	189
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	180
AS269163	L. O. LEANDRO INTERNET - ME	Unclassified	IPv4	180
AS33182	HostDime.com, Inc.	Hosting	IPv4 IPv6	95
AS28126	BRISANET SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv4	61
AS262805	REDE MINAS TELECOM LTDA	Unclassified	IPv4	61
AS28368	unnamed	Residential	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS262805	REDE MINAS TELECOM LTDA	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS270403	LOCAL TELECOM LTDA	Unclassified	IPv4 IPv6	376
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4	222
AS273440	JMT TELECOM - C DE SOUSA BEZERRA	Unclassified	IPv4	189
AS269163	L. O. LEANDRO INTERNET - ME	Unclassified	IPv4	180
AS262805	REDE MINAS TELECOM LTDA	Unclassified	IPv4	122
AS33182	HostDime.com, Inc.	Hosting	IPv4 IPv6	95
AS28126	BRISANET SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv4	61
AS28598	DB3 SERVICOS DE TELECOMUNICACOES S.A	Residential	IPv4	19
AS28368	unnamed	Residential	IPv4	3

Provenance

Where this comes from

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