Incidents | Studio Yeonhong Incidents reported on status page for Studio Yeonhong https://status.yeonhong.studio/en en KOREA_3 recovered https://status.yeonhong.studio/en Thu, 14 May 2026 17:06:33 +0000 https://status.yeonhong.studio/en#c2fc1cb00260cef22441520b62602841dacc5be4acfcd272b53c271b666e77cc KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Thu, 14 May 2026 17:06:15 +0000 https://status.yeonhong.studio/en#ca3a31e241e4080a9af80424723ca02afca10b4b286673a1c73e058b07848bee KOREA_2 recovered KOREA_1 recovered https://status.yeonhong.studio/en Thu, 14 May 2026 17:06:11 +0000 https://status.yeonhong.studio/en#d849dc2699c31b174a8087940ee6c50414e50e426262eaed1cff8170848be743 KOREA_1 recovered KOREA_3 went down https://status.yeonhong.studio/en Thu, 14 May 2026 16:58:24 +0000 https://status.yeonhong.studio/en#c2fc1cb00260cef22441520b62602841dacc5be4acfcd272b53c271b666e77cc KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Thu, 14 May 2026 16:58:08 +0000 https://status.yeonhong.studio/en#ca3a31e241e4080a9af80424723ca02afca10b4b286673a1c73e058b07848bee KOREA_2 went down KOREA_1 went down https://status.yeonhong.studio/en Thu, 14 May 2026 16:57:54 +0000 https://status.yeonhong.studio/en#d849dc2699c31b174a8087940ee6c50414e50e426262eaed1cff8170848be743 KOREA_1 went down KOREA_3 recovered https://status.yeonhong.studio/en Thu, 14 May 2026 15:24:32 +0000 https://status.yeonhong.studio/en#4b91d8b7245bac742018c0cd2a064762ad01ad6456ddefc83318ba79ec221d30 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Thu, 14 May 2026 15:24:09 +0000 https://status.yeonhong.studio/en#a7c60a1906ae3c43b250161c2618f6dc712ba348808640d9341ad764ffe1b710 KOREA_2 recovered KOREA_3 went down https://status.yeonhong.studio/en Thu, 14 May 2026 15:22:24 +0000 https://status.yeonhong.studio/en#4b91d8b7245bac742018c0cd2a064762ad01ad6456ddefc83318ba79ec221d30 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Thu, 14 May 2026 15:22:18 +0000 https://status.yeonhong.studio/en#a7c60a1906ae3c43b250161c2618f6dc712ba348808640d9341ad764ffe1b710 KOREA_2 went down Bot Server went down https://status.yeonhong.studio/en Mon, 23 Feb 2026 13:08:23 +0000 https://status.yeonhong.studio/en#276dfaafd645fc872ae818fd42e3be1279b8629aa147ea2fd0cdeb9b26c97335 Bot Server went down Main TTS API went down https://status.yeonhong.studio/en Sun, 08 Feb 2026 14:38:22 +0000 https://status.yeonhong.studio/en#98396d92dcd037d73adac012a46d6339ac8cf041101de5b06c143cb33e045fff Main TTS API 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 - 점검이 진행될때 목소리 끊김, 메시지를 읽지 않거나 연홍이가 나가지는 문제가 발생할 수 있어요 - 점검 시간은 단축되거나 연장되는 일정 변동이 발생할 수 있어요