On March 3, 2026, Studio.Design experienced a system issue that caused some legitimate user accounts to be mistakenly deactivated (treated as closed). As a result, public sites those users belonged to were automatically set to private. This incident has now been fully resolved, and corrective measures have been put in place.
■ Impact - Some legitimate user accounts were accidentally deactivated. - Public sites that those users belonged to were automatically set to private. - Unless site owners manually republished their sites, those sites were not accessible to visitors.
■ Timeframe (JST) March 3, 2026 (Tue) 6:00 pm to 8:20 pm
■ Current status - All user accounts that were mistakenly deactivated have been fully restored. - Sites that were set to private are not automatically republished.
If you wish your site to be public again, please republish it from your Studio.Design dashboard by following the steps below. 1. Open the affected project and open the Publish panel. 2. In the top-right of the Publish panel, click the “Publish” button. 3. When publishing is complete, a confirmation popup will appear. 4. Click the published URL and confirm that your site loads correctly.
■ Root cause We recently introduced additional account control logic to help protect Studio.Design from abusive use. Due to an error in this internal logic, some legitimate user accounts were incorrectly flagged as spam and deactivated. As a side effect, public sites those users belonged to were automatically set to private.
■ Prevention and follow‑up - Strengthening how we design, review, and test our account protection logic before it is deployed to the production environment. - Enhancing our monitoring and alerting so that, if similar misclassifications occur in the future, we can detect and resolve them much earlier.
We sincerely apologize that this issue affected your account and public sites, and for the inconvenience it caused.
Posted Mar 04, 2026 - 00:15 JST
This incident affected: Hosted Websites, Editor, Dashboard, and Live Preview.