asn.dev

Observed topology

AS264552 AS264552 - JustWeb Telecomunicacoes LTDA

Residential LACNIC Cable/DSL/ISP

Upstreams 3 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 4
Adjacent (IPv6) 2
Upstream graph Who carries AS264552, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS264552 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264552: 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.

ASNetworkTypeFamiliesPaths seen
AS28656BTT TELECOMUNICACOES S.A.ResidentialIPv4 IPv6385
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6106
AS264228BTT TELECOMUNICACOES S.A.ResidentialIPv440

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262504Nova Rede de Telecomunicacoes LtdaResidentialIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28656BTT TELECOMUNICACOES S.A.ResidentialIPv4 IPv6500
AS262504Nova Rede de Telecomunicacoes LtdaResidentialIPv4118
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6109
AS264228BTT TELECOMUNICACOES S.A.ResidentialIPv440

Provenance

Where this comes from

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