asn.dev

Observed topology

AS57578 MISAKA-CIS-AS Misaka Network, Inc.

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57578: 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
AS210756EdgeCenter LLCHostingIPv4 IPv6424
AS56630Melbikomas UABHostingIPv4 IPv6194
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6107
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv634
AS9002RETN LimitedUnclassifiedIPv4 IPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51044Kazuki YamaguchiUnclassifiedIPv4 IPv6164
AS202479iFog GmbHResidentialIPv659
AS57695Misaka Network, Inc.UnclassifiedIPv633
AS44406LLC Beliy MostUnclassifiedIPv630
AS50069Misaka Network, Inc.HostingIPv4 IPv616
AS135103Alex NeoUnclassifiedIPv67
AS216096Alex Terrats Ciberseguretat SLUUnclassifiedIPv63
AS207419Richard MarinoUnclassifiedIPv41

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS210756EdgeCenter LLCHostingIPv4 IPv6520
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6313
AS56630Melbikomas UABHostingIPv4 IPv6200
AS51044Kazuki YamaguchiUnclassifiedIPv4 IPv6164
AS202479iFog GmbHResidentialIPv659
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv634
AS57695Misaka Network, Inc.UnclassifiedIPv633
AS44406LLC Beliy MostUnclassifiedIPv630
AS50069Misaka Network, Inc.HostingIPv4 IPv616
AS9002RETN LimitedUnclassifiedIPv4 IPv613

All 13 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.