Observed topology

AS264049 TELECOMUNICACOES ALARCAO E FERNANDES LTDA - ME

Unclassified LACNIC

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264049: 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
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	291
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	88
AS267613	ELETRONET S.A.	Unclassified	IPv4	59
AS61621	Norte.Net Telecomunicacoes Ltda	Unclassified	IPv4	38
AS268554	CDM TELECOM	Unclassified	IPv4 IPv6	22
AS262588	EXPLORERNET INFOLINK TECNOLOGIA E TELECOMUNICACOES	Residential	IPv4	11

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS268554	CDM TELECOM	Unclassified	IPv4 IPv6	69

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS263558	RD TELECOM LTDA -ME	Residential	IPv4 IPv6	349
AS268554	CDM TELECOM	Unclassified	IPv4 IPv6	91
AS14840	BR.Digital Telecom	Unclassified	IPv4 IPv6	88
AS267613	ELETRONET S.A.	Unclassified	IPv4	59
AS61621	Norte.Net Telecomunicacoes Ltda	Unclassified	IPv4	38
AS262588	EXPLORERNET INFOLINK TECNOLOGIA E TELECOMUNICACOES	Residential	IPv4	22

Provenance

Where this comes from

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