asn.dev

Observed topology

AS209605 hostbaltic UAB Host Baltic

Hosting Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209605: 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
AS133398Tele Asia LimitedUnclassifiedIPv4400
AS9002RETN LimitedUnclassifiedIPv4 IPv6202
AS3303Swisscom (Schweiz) AGResidentialIPv410
AS6939Hurricane Electric LLCTransitIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209101IP Vendetta Inc.HostingIPv459
AS213790Limited Network LTDHostingIPv459
AS58232Parsun Network Solutions PTY LTDUnclassifiedIPv451
AS209425KOI CLOUD SERVICES (Pty) LtdUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133398Tele Asia LimitedUnclassifiedIPv4400
AS9002RETN LimitedUnclassifiedIPv4 IPv6345
AS209101IP Vendetta Inc.HostingIPv459
AS213790Limited Network LTDHostingIPv459
AS58232Parsun Network Solutions PTY LTDUnclassifiedIPv451
AS6939Hurricane Electric LLCTransitIPv432
AS3303Swisscom (Schweiz) AGResidentialIPv416
AS209425KOI CLOUD SERVICES (Pty) LtdUnclassifiedIPv44

Provenance

Where this comes from

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