Observed topology
AS57695 MISAKA Misaka Network, Inc.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS57695: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 442 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv6 | 366 |
| AS23961 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 228 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 161 |
| AS57578 | Misaka Network, Inc. | Hosting | IPv6 | 33 |
| AS142616 | Misaka Network, Inc. | Unclassified | IPv6 | 32 |
| AS32097 | WholeSale Internet, Inc. | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS57695 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58339 | MARIA STYLE LTD | Unclassified | IPv6 | 672 |
| AS44406 | LLC Beliy Most | Unclassified | IPv6 | 561 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv4 | 181 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 152 |
| AS50069 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 91 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv6 | 90 |
| AS23961 | Misaka Network, Inc. | Unclassified | IPv4 | 76 |
| AS207278 | Michael Hayler | Unclassified | IPv6 | 64 |
| AS203997 | XTDef Limited | Unclassified | IPv4 | 60 |
| AS34939 | NextDNS, Inc. | Hosting | IPv4 IPv6 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS57695 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 1,644 |
| AS917 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 1,469 |
| AS58339 | MARIA STYLE LTD | Unclassified | IPv6 | 672 |
| AS44406 | LLC Beliy Most | Unclassified | IPv6 | 561 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 423 |
| AS23961 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 370 |
| AS50069 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 91 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv6 | 90 |
| AS32097 | WholeSale Internet, Inc. | Hosting | IPv4 IPv6 | 70 |
| AS207278 | Michael Hayler | Unclassified | IPv6 | 64 |
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.