asn.dev

Observed topology

AS142616 MNI-AS-AP Misaka Network, Inc.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142616: 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
AS60068Datacamp LimitedHostingIPv4 IPv6221
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv6194

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS401339YAMATO CLOUD LLCHostingIPv479
AS23961Misaka Network, Inc.UnclassifiedIPv460
AS136180Beijing Tiantexin Tech. Co., Ltd.UnclassifiedIPv456
AS34939NextDNS, Inc.HostingIPv435
AS57695Misaka Network, Inc.UnclassifiedIPv633
AS43357Owl LimitedUnclassifiedIPv631
AS51044Kazuki YamaguchiUnclassifiedIPv421
AS931HyonixHostingIPv418
AS40806GrapheneOS FoundationHostingIPv4 IPv64
AS49904Xiaodong QiUnclassifiedIPv61

All 11 downstreams →

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6513
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv6301
AS401339YAMATO CLOUD LLCHostingIPv479
AS136180Beijing Tiantexin Tech. Co., Ltd.UnclassifiedIPv456
AS34939NextDNS, Inc.HostingIPv435
AS57695Misaka Network, Inc.UnclassifiedIPv633
AS43357Owl LimitedUnclassifiedIPv631
AS51044Kazuki YamaguchiUnclassifiedIPv421
AS931HyonixHostingIPv418
AS40806GrapheneOS FoundationHostingIPv4 IPv64

All 12 adjacent →

Provenance

Where this comes from

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