Observed topology

AS28165 Wireless Comm Services LTDA

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28165: 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
AS273490	INTERNET LTDA	Unclassified	IPv4 IPv6	938

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52890	Integrado de Telematica do Exercito	Unclassified	IPv4	145
AS264982	Telecom LTDA	Unclassified	IPv4 IPv6	91
AS270710	de Computacao da Aeronautica de Brasilia	Unclassified	IPv4	63
AS268786	FIBRA TELECOM LTDA	Unclassified	IPv4	60
AS271016	ME	Unclassified	IPv4	59
AS263403	AVENIDA SA	Unclassified	IPv4	17

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS273490	INTERNET LTDA	Unclassified	IPv4 IPv6	1,373
AS52890	Integrado de Telematica do Exercito	Unclassified	IPv4	145
AS264982	Telecom LTDA	Unclassified	IPv4 IPv6	91
AS270710	de Computacao da Aeronautica de Brasilia	Unclassified	IPv4	63
AS268786	FIBRA TELECOM LTDA	Unclassified	IPv4	60
AS271016	ME	Unclassified	IPv4	59
AS263403	AVENIDA SA	Unclassified	IPv4	17

Provenance

Where this comes from

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