AS917 Misaka Network, Inc.
AS917 (MISAKA) is registered to Misaka Network, Inc. in US, through ARIN. It originates 42 prefixes in the global routing table.
Who holds AS917
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
WHOIS recordARIN
# # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/resources/registry/whois/tou/ # # If you see inaccuracies in the results, please report at # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/ # # Copyright 1997-2026, American Registry for Internet Numbers, Ltd. # ASNumber: 917 ASName: MISAKA ASHandle: AS917 RegDate: 2022-06-13 Updated: 2023-01-01 Comment: For more details, please take a look at AS917's IRR record: Comment: # whois -h rr.arin.net AS917 Ref: https://rdap.arin.net/registry/autnum/917 OrgName: Misaka Network, Inc. OrgId: MN-321 Address: 8 The Green, Suite 6288 City: Dover StateProv: DE PostalCode: 19901 Country: US RegDate: 2019-01-07 Updated: 2024-11-25 Ref: https://rdap.arin.net/registry/entity/MN-321 OrgAbuseHandle: ABUSE8811-ARIN OrgAbuseName: Abuse OrgAbusePhone: +1-302-659-8081 OrgAbuseEmail: abuse-arin@misaka.email OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE8811-ARIN OrgNOCHandle: NOC32920-ARIN OrgNOCName: Network Operations Center OrgNOCPhone: +1-302-659-8081 OrgNOCEmail: noc@misaka.io OrgNOCRef: https://rdap.arin.net/registry/entity/NOC32920-ARIN OrgTechHandle: NOC32920-ARIN OrgTechName: Network Operations Center OrgTechPhone: +1-302-659-8081 OrgTechEmail: noc@misaka.io OrgTechRef: https://rdap.arin.net/registry/entity/NOC32920-ARIN # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/resources/registry/whois/tou/ # # If you see inaccuracies in the results, please report at # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/ # # Copyright 1997-2026, American Registry for Internet Numbers, Ltd. #
What AS917 announces
Prefixes originated by AS917 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS917 buys transit from
Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 14 upstreams.
Who AS917 exchanges routes with
1 peer: networks of comparable size it swaps its own and its customers’ routes with. Most peerings never reach a route collector, so this is the visible part.
Who buys transit from AS917
64 downstreams, its customers; those marked ASPA name AS917 as a provider in theirs.
Show 24 more
Provider authorization
AS917 publishes no ASPA of its own. 6 ASes name it as a provider in theirs. Check a path.
The 6 ASes that name AS917 as a provider
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
| Source | as-name | Maintained by |
|---|---|---|
| ARIN | MISAKA | MNT-MN-321 |
Route objects with origin AS917: RIPE 41 · ARIN 22 · APNIC 3 · RADB 1