asn.dev

Observed topology

AS268490 A.I.P. INTERNET

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268490: 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
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6256
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6114
AS264273A & G TELECOMUNICACOES LTDA EPPUnclassifiedIPv4 IPv650
AS265385Interline ProvedorUnclassifiedIPv4 IPv644
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv629
AS52579TELLIUS & ALLNET TELECOMUNICACOES DAS AMERICASHostingIPv4 IPv616
AS1031PEER 1031 LLCUnclassifiedIPv412

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22381SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv6256
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv6114
AS264273A & G TELECOMUNICACOES LTDA EPPUnclassifiedIPv4 IPv650
AS265385Interline ProvedorUnclassifiedIPv4 IPv644
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv629
AS52579TELLIUS & ALLNET TELECOMUNICACOES DAS AMERICASHostingIPv4 IPv616
AS1031PEER 1031 LLCUnclassifiedIPv412

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 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.