asn.dev

Observed topology

AS265484 AS265484 - CLICK ENTER LTDA - ME

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265484: 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
AS262462Aranet PlayUnclassifiedIPv4 IPv6607
AS6939Hurricane Electric LLCTransitIPv4 IPv6288
AS269194ST1 INTERNETResidentialIPv4 IPv6268
AS274789LUSOTEC NET EIRELIUnclassifiedIPv4 IPv663
AS24482SG.GSHostingIPv4 IPv626

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271287Intercom Informatica LTDA MEUnclassifiedIPv4 IPv6130
AS271540J C V A LEAL INFORMATICA LTDAUnclassifiedIPv4124
AS270707LINK NET BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv695
AS271084TRYMNET PROVEDORUnclassifiedIPv4 IPv621
AS274789LUSOTEC NET EIRELIUnclassifiedIPv621

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS262462Aranet PlayUnclassifiedIPv4 IPv6932
AS269194ST1 INTERNETResidentialIPv4 IPv6367
AS6939Hurricane Electric LLCTransitIPv4 IPv6325
AS271287Intercom Informatica LTDA MEUnclassifiedIPv4 IPv6178
AS271540J C V A LEAL INFORMATICA LTDAUnclassifiedIPv4124
AS270707LINK NET BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv695
AS274789LUSOTEC NET EIRELIUnclassifiedIPv4 IPv688
AS271084TRYMNET PROVEDORUnclassifiedIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv632
AS61621Norte.Net Telecomunicacoes LtdaUnclassifiedIPv62

All 11 adjacent →

Provenance

Where this comes from

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