Resolved -
We identified that it was a DNS-related issue and have resolved the problem.
Jun 12, 10:32 KST
Monitoring -
The issue is being monitored and the service is now operating normally.
Jun 12, 10:26 KST
Investigating -
We are currently investigating this issue.
Jun 12, 07:03 KST