Hello, this is the Melting Operations Team.

First and foremost, we sincerely apologize for the extended service disruption caused by an unexpected technical issue during our database migration. We are pleased to inform you that all recovery work and stability testing have been completed, and the service has been fully restored.

In the interest of transparency and to rebuild your trust in our service, we would like to share the details of the incident and our response.

1. Cause of the Incident Today's maintenance was a database environment migration aimed at improving service performance and strengthening our incident response capabilities. Despite multiple rounds of internal testing prior to the migration, an unexpected system crash was discovered immediately after switching to the new environment — one that only occurred when large-scale data processing coincided with specific search conditions.

This was an exceptional situation that could not be reproduced in the pre-maintenance test environment. However, with data safety and zero data loss as our absolute top priority, resolving the root cause required additional time, which led to the extended recovery delay.

2. Service Restoration Confirmed We have confirmed that all features are functioning normally in the new database environment, and have verified that all user data has been safely preserved without any loss.

• Incident period: Thursday, May 21, 2026, 08:00 – 11:33 (KST)

Through this infrastructure migration, Melting has established a more robust and faster service foundation.

However, as the service operator, we feel a deep sense of responsibility for exceeding the planned maintenance window and causing prolonged inconvenience to our users. We will thoroughly review our operational processes to ensure this does not happen again, and we are committed to earning back your trust through a more stable service.

Thank you.

Melting Operations Team