asn.dev

Observed topology

AS58791 GMOOSK-NET GMO Internet Group, Inc.

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58791: 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
AS13335Cloudflare, Inc.HostingIPv410,270
AS2914NTT America, Inc.TransitIPv4 IPv6649
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6516
AS6939Hurricane Electric LLCTransitIPv4201
AS7506GMO Internet, Inc.HostingIPv656

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58651GMO Internet, Inc.UnclassifiedIPv4 IPv694
AS55907GMO Internet, Inc.UnclassifiedIPv450

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv410,270
AS2914NTT America, Inc.TransitIPv4 IPv6721
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6542
AS6939Hurricane Electric LLCTransitIPv4219
AS58651GMO Internet, Inc.UnclassifiedIPv4 IPv694
AS7506GMO Internet, Inc.HostingIPv684
AS55907GMO Internet, Inc.UnclassifiedIPv450

Provenance

Where this comes from

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