asn.dev

Observed topology

AS201789 NETOPS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201789: 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
AS50673Serverius Holding B.V.UnclassifiedIPv4119
AS6939Hurricane Electric LLCTransitIPv4 IPv667
AS9002RETN LimitedUnclassifiedIPv4 IPv644
AS174Cogent Communications, LLCTransitIPv4 IPv623
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4 IPv622
AS1836green.ch AGResidentialIPv41
AS24482SG.GSHostingIPv41
AS48362Stadtwerke FeldkirchResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51430AltusHost B.V.UnclassifiedIPv4 IPv62,357
AS136787PacketHub S.A.VPNIPv4184
AS61295NETOPS B.V.UnclassifiedIPv465
AS207604United Internet Ltd.UnclassifiedIPv459

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS51430AltusHost B.V.UnclassifiedIPv4 IPv62,357
AS12459NETOPS B.V.HostingIPv4 IPv61,024
AS6939Hurricane Electric LLCTransitIPv4 IPv6822
AS9002RETN LimitedUnclassifiedIPv4 IPv6398
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6389
AS136787PacketHub S.A.VPNIPv4184
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS59900Balkan Internet Exchange LtdUnclassifiedIPv4 IPv6102
AS61295NETOPS B.V.UnclassifiedIPv465
AS207604United Internet Ltd.UnclassifiedIPv459

All 13 adjacent →

Provenance

Where this comes from

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