Observed topology
AS917 MISAKA - Misaka Network, Inc.
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS917: 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 | 1,034 |
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 370 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 236 |
| AS57695 | Misaka Network, Inc. | Unclassified | IPv4 | 175 |
| AS6233 | xTom | Hosting | IPv4 IPv6 | 88 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv6 | 31 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 8 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS917 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS931 | Hyonix | Hosting | IPv4 | 1,501 |
| AS48539 | Bifrost Systems OU | Unclassified | IPv4 IPv6 | 1,453 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 603 |
| AS57695 | Misaka Network, Inc. | Unclassified | IPv6 | 366 |
| AS969 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 356 |
| AS834 | IPXO LLC | Unclassified | IPv4 IPv6 | 320 |
| AS50069 | Misaka Network, Inc. | Hosting | IPv4 IPv6 | 200 |
| AS57196 | Clonoth OU | Unclassified | IPv4 IPv6 | 172 |
| AS205398 | Tyler Obrien | Unclassified | IPv6 | 172 |
| AS203314 | HATS NETWORK INC. | Residential | IPv6 | 157 |
Adjacency
Adjacent networks
Every AS seen directly next to AS917 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 4,155 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,098 |
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 2,094 |
| AS57695 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 1,461 |
| AS48539 | Bifrost Systems OU | Unclassified | IPv4 IPv6 | 1,453 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,300 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 910 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 693 |
| AS35487 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 634 |
| AS969 | Misaka Network, Inc. | Unclassified | IPv4 IPv6 | 356 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.