Incidents | Studio Yeonhong Incidents reported on status page for Studio Yeonhong https://status.yeonhong.studio/en en DB Server recovered https://status.yeonhong.studio/en Mon, 30 Jun 2025 09:44:53 +0000 https://status.yeonhong.studio/en#9312587f097ea54550ccce4f726ce032818ba09e7e2a69a644793309832bfe47 DB Server recovered DB Server went down https://status.yeonhong.studio/en Mon, 30 Jun 2025 09:41:45 +0000 https://status.yeonhong.studio/en#9312587f097ea54550ccce4f726ce032818ba09e7e2a69a644793309832bfe47 DB Server went down Main Server recovered https://status.yeonhong.studio/en Fri, 13 Jun 2025 21:10:15 +0000 https://status.yeonhong.studio/en#a557f942f9326f2a4d96bf798e501b3ca346b64bf05080a0a4e4184255f835ec Main Server recovered Main Server went down https://status.yeonhong.studio/en Fri, 13 Jun 2025 21:08:15 +0000 https://status.yeonhong.studio/en#a557f942f9326f2a4d96bf798e501b3ca346b64bf05080a0a4e4184255f835ec Main Server went down GCP API recovered https://status.yeonhong.studio/en Thu, 12 Jun 2025 19:08:48 +0000 https://status.yeonhong.studio/en#c6b1cd93948d6b4544d0b6e0e3cfb26213cbaeba4370376fe1629f743ec88e91 GCP API recovered GCP API went down https://status.yeonhong.studio/en Thu, 12 Jun 2025 18:20:46 +0000 https://status.yeonhong.studio/en#c6b1cd93948d6b4544d0b6e0e3cfb26213cbaeba4370376fe1629f743ec88e91 GCP API went down 홈페이지 recovered https://status.yeonhong.studio/en Mon, 09 Jun 2025 06:55:09 +0000 https://status.yeonhong.studio/en#bc34cd999f5b10c08172b02815f1eb8c22768028934bc8bdb919ac57d3472263 홈페이지 recovered Main Server recovered https://status.yeonhong.studio/en Mon, 09 Jun 2025 06:53:48 +0000 https://status.yeonhong.studio/en#f270cf5a9da92297f554e8c3cba2a54bd5c70d62aad47500a667053369dabb03 Main Server recovered 홈페이지 went down https://status.yeonhong.studio/en Sat, 07 Jun 2025 01:21:56 +0000 https://status.yeonhong.studio/en#bc34cd999f5b10c08172b02815f1eb8c22768028934bc8bdb919ac57d3472263 홈페이지 went down Main Server went down https://status.yeonhong.studio/en Sat, 07 Jun 2025 01:20:41 +0000 https://status.yeonhong.studio/en#f270cf5a9da92297f554e8c3cba2a54bd5c70d62aad47500a667053369dabb03 Main Server went down Main Server recovered https://status.yeonhong.studio/en Tue, 03 Jun 2025 11:43:15 +0000 https://status.yeonhong.studio/en#7e55465282d9072e29be454ccc58121d00ae62b4e6bca674373fcde93c9f3293 Main Server recovered Main Server went down https://status.yeonhong.studio/en Tue, 03 Jun 2025 11:40:15 +0000 https://status.yeonhong.studio/en#7e55465282d9072e29be454ccc58121d00ae62b4e6bca674373fcde93c9f3293 Main Server went down Main Server recovered https://status.yeonhong.studio/en Sat, 24 May 2025 04:44:35 +0000 https://status.yeonhong.studio/en#9d8dd2dcbc5257b90f93124c49cb9722386122178fbe2524c16a593ea773e2bd Main Server recovered Main Server went down https://status.yeonhong.studio/en Sat, 24 May 2025 04:41:10 +0000 https://status.yeonhong.studio/en#9d8dd2dcbc5257b90f93124c49cb9722386122178fbe2524c16a593ea773e2bd Main Server went down Main Server recovered https://status.yeonhong.studio/en Mon, 28 Apr 2025 06:26:04 +0000 https://status.yeonhong.studio/en#95b4936d6581e9ac2fa34dbad04c47a83dd16cc75982d80995a575fd814349ca Main Server recovered Main Server went down https://status.yeonhong.studio/en Mon, 28 Apr 2025 06:23:00 +0000 https://status.yeonhong.studio/en#95b4936d6581e9ac2fa34dbad04c47a83dd16cc75982d80995a575fd814349ca Main Server went down 연홍 봇 점검 안내 https://status.yeonhong.studio/en/incident/542338 Thu, 10 Apr 2025 02:40:14 +0000 https://status.yeonhong.studio/en/incident/542338#689061d1fe53b7af6be48378a1b1873e0508d6c31b59f08023c31f3ca7b5ab5b Maintenance completed 연홍 봇 점검 안내 https://status.yeonhong.studio/en/incident/542338 Thu, 10 Apr 2025 02:30:14 -0000 https://status.yeonhong.studio/en/incident/542338#53a81fbc77a954311dba8c4755fc039c5d17dec0988323baff3d2d8d7c70e03c - 점검이 진행될때 목소리 끊김, 메시지를 읽지 않거나 연홍이가 나가지는 문제가 발생할 수 있어요 - 점검 시간은 단축되거나 연장되는 일정 변동이 발생할 수 있어요