AS917

AS917 is an actively routed autonomous system whose operator is Unknown: no reachable, first-party source names a registrant or operating company for this ASN as of an August 2026 search. As observed by the RouteViews route collector on 2026-08-20, it originates 27 IPv4 prefixes and 15 IPv6 prefixes — an estimated 9,472 IPv4 addresses and 13,829 IPv6 /48-equivalents — with 76 distinct neighboring ASNs seen in the same observation, confirming this is an actively routed network rather than a dormant registration.

A prior version of this entry bound AS917 to "Misaka Network, Inc." on two docs.misaka.io pages. Re-checked live this pass, docs.misaka.io, www.misaka.io, app.misaka.io, and bare misaka.io all resolve only to RFC 5737 and RFC 3849 documentation-block addresses from multiple independent resolvers, and a direct HTTPS fetch fails certificate validation — no Misaka content is retrievable by any client. A control domain resolved normally in the same run, so this is specific to those hosts, not a general lookup failure.

A separate, genuinely reachable page describing an operator named "Misaka" was checked as a corroboration attempt and came back negative: it contains zero occurrences of "AS917" or of any related ASN number, so nothing that actually loads ties this ASN to that or any other named operator. Country, network type, notable usage, peering policy, related ASNs, organizational status, website, and geographic footprint are therefore all Unknown, not merely undocumented.

Relationship direction comes from a separate dataset on a different day. The CAIDA AS Relationships cache (dataset date 2026-08-01) infers AS1299, AS3356, and AS60068 as transit providers to AS917, AS112 as a customer, and 19 settlement-free peers among the 76 neighboring ASNs RouteViews observed — an inference from observed AS paths, not a disclosed peering agreement, and a floor rather than a census.

The IANA AS Number registry places AS917 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. Allocation date, RPKI validation posture, internet-exchange presence, assignment class, and a registered abuse contact all remain Unknown as of 2026-08.

Blocklist status

No ASN-wide blocklisting found in Spamhaus DROP/ASN-DROP-style reporting naming AS917 as of an August 2026 search — spamhaus.org.

Community reputation

Withdrawn this cycle — a Trustpilot rating and an operator status-history page cited in a prior version were attributed to AS917 only through the operator binding above, and neither page names AS917, so neither is retained as a finding about this ASN.

Operator

Unknown — no reachable, first-party source names an operator for AS917 as of an August 2026 search; the technical-documentation pages a prior version cited resolve only to non-routable documentation-block addresses, not live content [Unknown]

Country / RIR

Country Unknown — no first-party registration record found [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS917 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876

Allocated

Unknown [Unknown]

Org status

Unknown — no reachable, first-party source confirms an operating organization for this ASN as of an August 2026 search [Unknown]

Contacts

Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above for abuse-signal, blocklist, and CVE/malware checks as of an August 2026 search

Network & routing

Network type

Unknown — no reachable, first-party source describes this network's product or business type as of an August 2026 search [Unknown]

Size

27 IPv4 prefixes and 15 IPv6 prefixes originated; an estimated 9,472 IPv4 addresses and 13,829 IPv6 /48-equivalents, as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS917

Routing/peering

76 distinct neighboring ASNs observed by RouteViews on 2026-08-20 (32-entry capped sample: AS834, AS906, AS931, AS969, AS976, AS1299, AS3130, AS3214, AS3356, AS3741, AS6233, AS6939, AS9002, AS12654, AS14570, AS17243, AS18464, AS21903, AS23121, AS23961, AS24785, AS26939, AS30671, AS33171, AS34939, AS35487, AS35930, AS37100, AS40806, AS44421, AS47553, AS48539); this is undirected AS-path adjacency, not a customer/upstream/peer classification. Relationship roles come separately from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA), which classifies 23 rows naming AS917 among published neighbours: 3 providers (AS1299, AS3356, AS60068), 1 customer (AS112), and 19 settlement-free peers. Those are CAIDA inferences from observed AS paths, not disclosed peering agreements, and a floor rather than a census. Peering policy: Unknown — no reachable first-party technical peering-policy page found [Confirmed for the neighbor count; Inferred for relationship roles; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS917, the cached registry snapshots/caida-as-rel.csv AS917

RPKI

Unknown — an unevaluated status, not a report of an absent or invalid ROA [Unknown]

Notable usage

Unknown — no reachable, first-party source describes this network's usage as of an August 2026 search [Unknown]

Related ASNs

Unknown — a prior version asserted AS57695 rested only on the same unreachable documentation pages and is not carried forward [Unknown]

Related fields

AS rank, customer cone size, RPKI validation status, and IX presence are all Unknown [Unknown]

Analyst note

Actively routed ASN observed by RouteViews on 2026-08-20 (27 IPv4 / 15 IPv6 prefixes, 76 neighboring ASNs); this is a single collector snapshot, not a registry-declared allocation size. Operator identity is Unknown as of an August 2026 search: the two pages a prior version cited for an operator name do not resolve to reachable content, and a separately reachable page describing a similarly named operator does not mention this ASN, so no binding is established. Upstreams AS1299, AS3356, and AS60068 are CAIDA-inferred transit providers among published neighbours (dataset date 2026-08-01, a separate observation from the RouteViews snapshot above), alongside 1 inferred customer (AS112) and 19 inferred settlement-free peers, stated as a floor rather than a census. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, exchange presence, assignment class, and abuse contacts are Unknown as of 2026-08.