asn.dev

Observed topology

AS264969 AS264969 - FD CAVALCANTE DE LIMA ME

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264969: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6150
AS37468Angola CablesUnclassifiedIPv4 IPv667
AS24482SG.GSHostingIPv4 IPv67
AS35280F5 Networks SARLHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269003KIMNET SOLUCOESUnclassifiedIPv4 IPv6237
AS269645WF CONNECTUnclassifiedIPv4118
AS269659RD TORRESNET TELECOM LTDAUnclassifiedIPv498
AS270855J.Z COSTA SILVA MEUnclassifiedIPv459
AS263427Carlos Henrique Santos de Oliveira MEUnclassifiedIPv450
AS28188Pronto Net Ltda.UnclassifiedIPv616

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6354
AS265038TELFO SERVICO DE TELECOMUNICACOES LTDAResidentialIPv4241
AS269003KIMNET SOLUCOESUnclassifiedIPv4 IPv6237
AS37468Angola CablesUnclassifiedIPv4 IPv6174
AS269645WF CONNECTUnclassifiedIPv4118
AS269659RD TORRESNET TELECOM LTDAUnclassifiedIPv498
AS270855J.Z COSTA SILVA MEUnclassifiedIPv459
AS263427Carlos Henrique Santos de Oliveira MEUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv620
AS28188Pronto Net Ltda.UnclassifiedIPv616

Provenance

Where this comes from

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