asn.dev

Observed topology

AS264169 AS264169 - WNP INTERNET

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264169: 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
AS262907BRASIL TECPAR AMIGO AVATOResidentialIPv4 IPv6589
AS266445SEA TELECOM LTDAUnclassifiedIPv4 IPv6168
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv658
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv433
AS263650Clicfacil TelecomUnclassifiedIPv432
AS6939Hurricane Electric LLCTransitIPv630
AS24482SG.GSHostingIPv4 IPv614
AS266337MARLON LIMA GOMES MEUnclassifiedIPv610
AS1031PEER 1031 LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263611ZUM TELECOM LTDA- MEUnclassifiedIPv481
AS268664MEGA TOP MULTIMIDIA LTDA-MEUnclassifiedIPv463

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS262907BRASIL TECPAR AMIGO AVATOResidentialIPv4 IPv6700
AS266445SEA TELECOM LTDAUnclassifiedIPv4 IPv6200
AS263611ZUM TELECOM LTDA- MEUnclassifiedIPv481
AS268664MEGA TOP MULTIMIDIA LTDA-MEUnclassifiedIPv463
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv658
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv433
AS263650Clicfacil TelecomUnclassifiedIPv432
AS6939Hurricane Electric LLCTransitIPv630
AS24482SG.GSHostingIPv4 IPv615
AS266337MARLON LIMA GOMES MEUnclassifiedIPv610

All 11 adjacent →

Provenance

Where this comes from

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