asn.dev

Observed topology

AS264906 AS264906 - PLANET INTERNET

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264906: 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 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv633
AS24482SG.GSHostingIPv45
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262811Mendex NetworksResidentialIPv4 IPv690

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6305
AS262811Mendex NetworksResidentialIPv4 IPv6265
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv688
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv643
AS24482SG.GSHostingIPv45
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Provenance

Where this comes from

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