asn.dev

Observed topology

AS52389 SSCS BV

Unclassified LACNIC NSP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS52389: 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 IPv679
AS174Cogent Communications, LLCTransitIPv4 IPv614
AS3216PJSC "Vimpelcom"MobileIPv41
AS3303Swisscom (Schweiz) AGResidentialIPv41
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS37100SEACOM LimitedUnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS48185team.blue NVUnclassifiedIPv41
AS48362Stadtwerke FeldkirchResidentialIPv41

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28104Eutel N.V.UnclassifiedIPv4858
AS63293Facebook, Inc.HostingIPv4 IPv6103
AS396950COLLECTIVITE DE SAINT BARTHELEMYUnclassifiedIPv455

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6911
AS28104Eutel N.V.UnclassifiedIPv4858
AS174Cogent Communications, LLCTransitIPv4 IPv6199
AS63293Facebook, Inc.HostingIPv4 IPv6103
AS396950COLLECTIVITE DE SAINT BARTHELEMYUnclassifiedIPv492
AS33392Dauphin TelecomResidentialIPv625
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS3303Swisscom (Schweiz) AGResidentialIPv416
AS24482SG.GSHostingIPv416
AS1103SURF B.V.UnclassifiedIPv415

All 17 adjacent →

Provenance

Where this comes from

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