asn.dev

Observed topology

AS28264 ADLLink Provedor de Internet Via Radio LTDA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28264: 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
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv6422
AS273499ORLANDO LEITE ROLIMUnclassifiedIPv463
AS273457WAVE LINK TELECOM LTDAUnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS52679VIRTUAL NET SERVICOS DE INFORMATICA LTDA - MEUnclassifiedIPv4 IPv6589
AS61767R. A TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4 IPv697
AS274679A2 CONNECT LTDAUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28126BRISANET SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4 IPv61,400
AS52679VIRTUAL NET SERVICOS DE INFORMATICA LTDA - MEUnclassifiedIPv4 IPv6684
AS273457WAVE LINK TELECOM LTDAUnclassifiedIPv4 IPv6180
AS61767R. A TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4 IPv697
AS274679A2 CONNECT LTDAUnclassifiedIPv4 IPv693
AS273499ORLANDO LEITE ROLIMUnclassifiedIPv463
AS263500Star Telecom S/AUnclassifiedIPv4 IPv616

Provenance

Where this comes from

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