asn.dev

Observed topology

AS27589 MOJOHOST

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27589: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6591
AS396998Path Network, Inc.UnclassifiedIPv4235
AS3257GTT Communications Inc.TransitIPv4 IPv6211
AS174Cogent Communications, LLCTransitIPv4 IPv6203
AS24482SG.GSHostingIPv4 IPv614
AS6939Hurricane Electric LLCTransitIPv44
AS20205Amplex Electric, Inc.ResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27229Webhosting.Net, Inc.HostingIPv4690
AS53292ManagedWayUnclassifiedIPv4 IPv6330
AS11110SERVERCLOUDHostingIPv4 IPv690
AS13477Neutral NetworksUnclassifiedIPv425

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,423
AS53292ManagedWayUnclassifiedIPv4 IPv6745
AS27229Webhosting.Net, Inc.HostingIPv4690
AS3257GTT Communications Inc.TransitIPv4 IPv6662
AS174Cogent Communications, LLCTransitIPv4 IPv6467
AS396998Path Network, Inc.UnclassifiedIPv4235
AS11110SERVERCLOUDHostingIPv4 IPv690
AS13477Neutral NetworksUnclassifiedIPv425
AS24482SG.GSHostingIPv4 IPv614
AS6939Hurricane Electric LLCTransitIPv46

All 11 adjacent →

Provenance

Where this comes from

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