Observed topology

AS28246 AS28246 - REDE SIVNET TELECOMUNICACOES LTDA

Unclassified LACNIC Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28246: 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	321
AS269194	ST1 INTERNET	Residential	IPv4	187
AS52878	REDE DE TELECOMUNICACOES CARAJAS LTDA	Unclassified	IPv4	177
AS6939	Hurricane Electric LLC	Transit	IPv4	108
AS263444	Open X Tecnologia Ltda	Unclassified	IPv4	108
AS53158	Net Turbo Telecom	Unclassified	IPv4	59
AS28368	unnamed	Residential	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52878	REDE DE TELECOMUNICACOES CARAJAS LTDA	Unclassified	IPv6	99

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS61832	DB3 SERVICOS DE TELECOMUNICACOES S.A	Unclassified	IPv4 IPv6	369
AS52878	REDE DE TELECOMUNICACOES CARAJAS LTDA	Unclassified	IPv4 IPv6	276
AS269194	ST1 INTERNET	Residential	IPv4 IPv6	190
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	156
AS263444	Open X Tecnologia Ltda	Unclassified	IPv4	108
AS53158	Net Turbo Telecom	Unclassified	IPv4	59
AS28368	unnamed	Residential	IPv4	2

Provenance

Where this comes from

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