Incidents | Studio Yeonhong Incidents reported on status page for Studio Yeonhong https://status.yeonhong.studio/en en KOREA_1 recovered https://status.yeonhong.studio/en Thu, 11 Sep 2025 16:37:05 +0000 https://status.yeonhong.studio/en#6b164f77d164821040f9cbfe3a686c2ecaba74363f1dfe60e369fc112faff185 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Thu, 11 Sep 2025 06:44:25 +0000 https://status.yeonhong.studio/en#6b164f77d164821040f9cbfe3a686c2ecaba74363f1dfe60e369fc112faff185 KOREA_1 went down KOREA_1 recovered https://status.yeonhong.studio/en Tue, 09 Sep 2025 18:08:20 +0000 https://status.yeonhong.studio/en#37c0870b626c7be1d2b0a3586d951ff6fb7a50ed478762f7080b0838f32a1dd9 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Tue, 09 Sep 2025 17:53:19 +0000 https://status.yeonhong.studio/en#37c0870b626c7be1d2b0a3586d951ff6fb7a50ed478762f7080b0838f32a1dd9 KOREA_1 went down KOREA_1 recovered https://status.yeonhong.studio/en Thu, 04 Sep 2025 13:19:26 +0000 https://status.yeonhong.studio/en#d42db43c245396020e9c97c1b2f9d09ab6a8b88ef818bd3b59749e19e538b7ab KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Thu, 04 Sep 2025 12:11:37 +0000 https://status.yeonhong.studio/en#d42db43c245396020e9c97c1b2f9d09ab6a8b88ef818bd3b59749e19e538b7ab KOREA_1 went down Bot Server recovered https://status.yeonhong.studio/en Thu, 04 Sep 2025 11:51:04 +0000 https://status.yeonhong.studio/en#24aa94f93789ac88530d4365c21b892c6d7110888b8a1ae4f5ed594f305da069 Bot Server recovered Bot Server went down https://status.yeonhong.studio/en Thu, 04 Sep 2025 11:47:59 +0000 https://status.yeonhong.studio/en#24aa94f93789ac88530d4365c21b892c6d7110888b8a1ae4f5ed594f305da069 Bot Server went down KOREA_1 recovered https://status.yeonhong.studio/en Sun, 31 Aug 2025 11:41:16 +0000 https://status.yeonhong.studio/en#a34e4bfb0912e5b351c8edbace3275328ec5a99715179ac59abf80bd195068a1 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sun, 31 Aug 2025 11:38:34 +0000 https://status.yeonhong.studio/en#a34e4bfb0912e5b351c8edbace3275328ec5a99715179ac59abf80bd195068a1 KOREA_1 went down KOREA_1 recovered https://status.yeonhong.studio/en Sat, 30 Aug 2025 09:17:13 +0000 https://status.yeonhong.studio/en#1349146c0a74d524a0453d8211af04d72f08db2c2204659206862f618523ec89 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sat, 30 Aug 2025 09:05:18 +0000 https://status.yeonhong.studio/en#1349146c0a74d524a0453d8211af04d72f08db2c2204659206862f618523ec89 KOREA_1 went down DB Server recovered https://status.yeonhong.studio/en Tue, 26 Aug 2025 13:33:37 +0000 https://status.yeonhong.studio/en#ed151ec1196d500dd52bd48a46c942bd5f7d6e58e2c2ba419fcf3243ec4e58e7 DB Server recovered DB Server went down https://status.yeonhong.studio/en Tue, 26 Aug 2025 13:26:03 +0000 https://status.yeonhong.studio/en#ed151ec1196d500dd52bd48a46c942bd5f7d6e58e2c2ba419fcf3243ec4e58e7 DB Server went down JAPAN_1 recovered https://status.yeonhong.studio/en Sun, 24 Aug 2025 20:14:21 +0000 https://status.yeonhong.studio/en#6a2e9ee02cd05663ef68a3eb9541e2a0dd5edbe68d8da295f3cfad1d661a70c4 JAPAN_1 recovered JAPAN_1 went down https://status.yeonhong.studio/en Sun, 24 Aug 2025 20:11:17 +0000 https://status.yeonhong.studio/en#6a2e9ee02cd05663ef68a3eb9541e2a0dd5edbe68d8da295f3cfad1d661a70c4 JAPAN_1 went down JAPAN_1 recovered https://status.yeonhong.studio/en Fri, 22 Aug 2025 14:43:33 +0000 https://status.yeonhong.studio/en#0297179f03bfe005235d7e16636c20882f35906ffc9864ece82df8dbc61b58a9 JAPAN_1 recovered JAPAN_1 went down https://status.yeonhong.studio/en Fri, 22 Aug 2025 14:40:38 +0000 https://status.yeonhong.studio/en#0297179f03bfe005235d7e16636c20882f35906ffc9864ece82df8dbc61b58a9 JAPAN_1 went down Bot Server recovered https://status.yeonhong.studio/en Mon, 21 Jul 2025 17:34:13 +0000 https://status.yeonhong.studio/en#a4b1ae6b840a3617e2a540df643ef386a5ba6ecd4ed33f5106ca787de74629d7 Bot Server recovered Bot Server went down https://status.yeonhong.studio/en Mon, 21 Jul 2025 17:32:15 +0000 https://status.yeonhong.studio/en#a4b1ae6b840a3617e2a540df643ef386a5ba6ecd4ed33f5106ca787de74629d7 Bot 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 - 점검이 진행될때 목소리 끊김, 메시지를 읽지 않거나 연홍이가 나가지는 문제가 발생할 수 있어요 - 점검 시간은 단축되거나 연장되는 일정 변동이 발생할 수 있어요