Observed topology

AS264100 RIO CABLE TELECOM LTDA

Residential ARIN

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264100: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	441
AS28210	GIGA MAIS FIBRA TELECOMUNICACOES S.A.	Residential	IPv4	158
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4	126
AS28296	Acessa Telecomunicacoes Ltda	Unclassified	IPv4	56
AS53181	Avanca Telecom e Servicos LTDA	Unclassified	IPv4 IPv6	47
AS35280	F5 Networks SARL	Hosting	IPv4	27

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS263008	RIO CABLE CORPORATE LTDA - ME	Unclassified	IPv4	210

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	581
AS28210	GIGA MAIS FIBRA TELECOMUNICACOES S.A.	Residential	IPv4	292
AS263008	RIO CABLE CORPORATE LTDA - ME	Unclassified	IPv4	210
AS28296	Acessa Telecomunicacoes Ltda	Unclassified	IPv4	154
AS263009	FORTE TELECOM LTDA.	Hosting	IPv4	137
AS53181	Avanca Telecom e Servicos LTDA	Unclassified	IPv4 IPv6	60
AS35280	F5 Networks SARL	Hosting	IPv4	37

Provenance

Where this comes from

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