Observed topology

AS28285 AS28285 - Beltraonet Telecomunicacoes LTDA - EPP

Unclassified APNIC NSP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28285: 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
AS274589	UNION TELECOMUNICACOES E SERVICOS LTDA	Unclassified	IPv4	180
AS264943	VIARAPIDA TELECOMUNICACOES LTDA - ME	Unclassified	IPv4 IPv6	136
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	77
AS262434	WIIP TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv6	8
AS24482	SG.GS	Hosting	IPv4 IPv6	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS61892	MONISAT SISTEMA DE INFORMACAO E MONITORAMENTO	Unclassified	IPv4	51

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS274589	UNION TELECOMUNICACOES E SERVICOS LTDA	Unclassified	IPv4	187
AS264943	VIARAPIDA TELECOMUNICACOES LTDA - ME	Unclassified	IPv4 IPv6	170
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	86
AS61892	MONISAT SISTEMA DE INFORMACAO E MONITORAMENTO	Unclassified	IPv4	51
AS262434	WIIP TELECOM SERVICOS DE INTERNET LTDA	Unclassified	IPv6	8
AS24482	SG.GS	Hosting	IPv4 IPv6	5

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.