asn.dev

Observed topology

AS60011 MYTHIC-BEASTS-USA Mythic Beasts Ltd

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60011: 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 IPv6230
AS3356Level 3 Parent, LLCTransitIPv4 IPv6100
AS58057Securebit AGUnclassifiedIPv62

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv667
AS31064SABRI-BERISHAUnclassifiedIPv464
AS212240RIK Networks LtdUnclassifiedIPv464
AS62538ipFail NetworksUnclassifiedIPv461
AS32639SolarNetOne, Inc.UnclassifiedIPv450
AS47002Tiger Technologies LLCHostingIPv4 IPv649
AS53356Free Range Cloud Hosting Inc.HostingIPv4 IPv642
AS210000TwentyWAN MBHostingIPv4 IPv614
AS397131Everythink Innovations LimitedHostingIPv412
AS22296Vorsk LLCUnclassifiedIPv410

All 11 downstreams →

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6498
AS3356Level 3 Parent, LLCTransitIPv4 IPv6382
AS34927iFog GmbHHostingIPv4 IPv6184
AS31064SABRI-BERISHAUnclassifiedIPv464
AS212240RIK Networks LtdUnclassifiedIPv464
AS62538ipFail NetworksUnclassifiedIPv461
AS32639SolarNetOne, Inc.UnclassifiedIPv450
AS47002Tiger Technologies LLCHostingIPv4 IPv649
AS53356Free Range Cloud Hosting Inc.HostingIPv4 IPv642
AS210000TwentyWAN MBHostingIPv4 IPv616

All 15 adjacent →

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.