asn.dev

Observed topology

AS264211 AS264211 - A C Gomes-ME

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264211: 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 IPv668
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv660
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv622

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265493HIPERLINK.NET SERVICOS DE COMUNICACAO LTDA - MEUnclassifiedIPv4 IPv6146
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv648

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS265493HIPERLINK.NET SERVICOS DE COMUNICACAO LTDA - MEUnclassifiedIPv4 IPv6146
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6136
AS529651TELECOM SERVICOS DE TECNOLOGIA EM INTERNET LTDAUnclassifiedIPv4 IPv661
AS262663METROFLEX TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv648
AS52468UFINET PANAMA S.A.UnclassifiedIPv41

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.