asn.dev

Observed topology

AS209046 AS-GAL Georgianairlink LLC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209046: 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
AS198150SIACOM JSCUnclassifiedIPv4336
AS20771Caucasus Online Ltd.UnclassifiedIPv4196
AS35805JSC "Silknet"UnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49016JSC Georgian State ElectrosystemUnclassifiedIPv4138
AS205173JSC "Georgian Railway"UnclassifiedIPv4104
AS199625Netcom LLCUnclassifiedIPv460
AS210234City Net LLCUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS198150SIACOM JSCUnclassifiedIPv4413
AS20771Caucasus Online Ltd.UnclassifiedIPv4357
AS35805JSC "Silknet"UnclassifiedIPv4182
AS49016JSC Georgian State ElectrosystemUnclassifiedIPv4138
AS205173JSC "Georgian Railway"UnclassifiedIPv4104
AS199625Netcom LLCUnclassifiedIPv460
AS210234City Net LLCUnclassifiedIPv459

Provenance

Where this comes from

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