asn.dev

Observed topology

AS50069 MISAKA-ANYCAST Misaka Network, Inc.

Hosting RIPE Content

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS50069: 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
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6188
AS931HyonixHostingIPv4 IPv6174
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv6107
AS57695Misaka Network, Inc.UnclassifiedIPv4 IPv690
AS35487Misaka Network, Inc.UnclassifiedIPv4 IPv682
AS213122Krixe Pte. Ltd.UnclassifiedIPv416
AS58313Misaka Network, Inc.UnclassifiedIPv4 IPv615
AS57578Misaka Network, Inc.HostingIPv4 IPv612
AS36236NetActuate, IncHostingIPv4 IPv610
AS48386Misaka Network, Inc.UnclassifiedIPv46

All 11 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6188
AS931HyonixHostingIPv4 IPv6174
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv6107
AS57695Misaka Network, Inc.UnclassifiedIPv4 IPv690
AS35487Misaka Network, Inc.UnclassifiedIPv4 IPv682
AS213122Krixe Pte. Ltd.UnclassifiedIPv416
AS58313Misaka Network, Inc.UnclassifiedIPv4 IPv615
AS57578Misaka Network, Inc.HostingIPv4 IPv612
AS36236NetActuate, IncHostingIPv4 IPv610
AS48386Misaka Network, Inc.UnclassifiedIPv46

All 11 adjacent →

Provenance

Where this comes from

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