asn.dev

Observed topology

AS266514 AS266514 - Antonio J De Albuquerque ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266514: 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
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6312
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6140
AS6939Hurricane Electric LLCTransitIPv498
AS265890GR SOLUCOES TELECOM LTDA - MEUnclassifiedIPv463
AS53087TELY Ltda.ResidentialIPv461
AS24482SG.GSHostingIPv411
AS35280F5 Networks SARLHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS271377Torres Alves e Brandao Ltda - MEUnclassifiedIPv4 IPv693
AS268590SEABANT DIGITAL LTDAUnclassifiedIPv4 IPv69

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6365
AS266129LOCALLINK TELECOMUNICACOES LTDA - MEResidentialIPv4 IPv6189
AS6939Hurricane Electric LLCTransitIPv498
AS271377Torres Alves e Brandao Ltda - MEUnclassifiedIPv4 IPv693
AS265890GR SOLUCOES TELECOM LTDA - MEUnclassifiedIPv463
AS53087TELY Ltda.ResidentialIPv461
AS24482SG.GSHostingIPv411
AS268590SEABANT DIGITAL LTDAUnclassifiedIPv4 IPv69
AS35280F5 Networks SARLHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

Provenance

Where this comes from

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