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 Tue, 24 Mar 2026 10:15:04 +0000 https://status.yeonhong.studio/en#6a360acacc008b6b666c0bc6c6fbe7e12f172371ea0312dcb6786eb1550737a9 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Tue, 24 Mar 2026 10:12:13 +0000 https://status.yeonhong.studio/en#6a360acacc008b6b666c0bc6c6fbe7e12f172371ea0312dcb6786eb1550737a9 KOREA_1 went down KOREA_3 recovered https://status.yeonhong.studio/en Mon, 02 Mar 2026 13:48:41 +0000 https://status.yeonhong.studio/en#cd77dd2c7013da3a2359befd50747c3969ccca8f1a8b6aa049d3eaf68efadc42 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Mon, 02 Mar 2026 13:48:11 +0000 https://status.yeonhong.studio/en#67872ba514a6d7c904413ab36797bd0af361fb348bd333a2d491c58c3a8e37e9 KOREA_2 recovered KOREA_3 went down https://status.yeonhong.studio/en Mon, 02 Mar 2026 13:33:29 +0000 https://status.yeonhong.studio/en#cd77dd2c7013da3a2359befd50747c3969ccca8f1a8b6aa049d3eaf68efadc42 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Mon, 02 Mar 2026 13:33:15 +0000 https://status.yeonhong.studio/en#67872ba514a6d7c904413ab36797bd0af361fb348bd333a2d491c58c3a8e37e9 KOREA_2 went down KOREA_1 recovered https://status.yeonhong.studio/en Mon, 02 Mar 2026 06:48:08 +0000 https://status.yeonhong.studio/en#9174bade46fb31280712184a425a9976e931258fa3b1ffdca6f17e4ab2217a99 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Mon, 02 Mar 2026 02:48:00 +0000 https://status.yeonhong.studio/en#9174bade46fb31280712184a425a9976e931258fa3b1ffdca6f17e4ab2217a99 KOREA_1 went down KOREA_3 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 19:24:33 +0000 https://status.yeonhong.studio/en#51300da5689f5f799fdf698209a4c6bb3de0bc1423054f9adfba5508d781e0f2 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 19:24:20 +0000 https://status.yeonhong.studio/en#1cdd87a4e868bb5c582d5c35a79339ed789fd084ecccbdafb436b408d710261f KOREA_2 recovered KOREA_1 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 19:24:07 +0000 https://status.yeonhong.studio/en#78c592240d7119c4748fc80e150f267a7a16497fb2505a30ad0d33a6d0e68bc3 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 11:09:04 +0000 https://status.yeonhong.studio/en#78c592240d7119c4748fc80e150f267a7a16497fb2505a30ad0d33a6d0e68bc3 KOREA_1 went down KOREA_3 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 11:03:36 +0000 https://status.yeonhong.studio/en#51300da5689f5f799fdf698209a4c6bb3de0bc1423054f9adfba5508d781e0f2 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 11:03:13 +0000 https://status.yeonhong.studio/en#1cdd87a4e868bb5c582d5c35a79339ed789fd084ecccbdafb436b408d710261f KOREA_2 went down KOREA_3 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 09:48:34 +0000 https://status.yeonhong.studio/en#76a4b8d1ab0e8893b1e1fdc01b5e2453958d949dca0f136f4f075f11d50c1249 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 09:48:19 +0000 https://status.yeonhong.studio/en#609f8dacfff37b52e5b760fb656ea11ebbc925046b3c93d1788658c0b135147a KOREA_2 recovered KOREA_3 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 09:33:36 +0000 https://status.yeonhong.studio/en#76a4b8d1ab0e8893b1e1fdc01b5e2453958d949dca0f136f4f075f11d50c1249 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 09:33:14 +0000 https://status.yeonhong.studio/en#609f8dacfff37b52e5b760fb656ea11ebbc925046b3c93d1788658c0b135147a KOREA_2 went down KOREA_1 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 08:48:03 +0000 https://status.yeonhong.studio/en#c585c36e4245c5d31821781f4fe6e9cce1eca2195fedc94c42f29612ee99121f KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 08:39:02 +0000 https://status.yeonhong.studio/en#c585c36e4245c5d31821781f4fe6e9cce1eca2195fedc94c42f29612ee99121f KOREA_1 went down KOREA_3 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 06:12:32 +0000 https://status.yeonhong.studio/en#dd0172ec946c4ed4c15b4eab9b92221a226b5974be53cedf28afaabe15ef4957 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 06:12:20 +0000 https://status.yeonhong.studio/en#2542cc8dd3d82ca4b0791e4d535afb323fb049a112a393e1dffefde6a9bd07da KOREA_2 recovered KOREA_3 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 05:36:32 +0000 https://status.yeonhong.studio/en#dd0172ec946c4ed4c15b4eab9b92221a226b5974be53cedf28afaabe15ef4957 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 05:36:19 +0000 https://status.yeonhong.studio/en#2542cc8dd3d82ca4b0791e4d535afb323fb049a112a393e1dffefde6a9bd07da KOREA_2 went down KOREA_1 recovered https://status.yeonhong.studio/en Sun, 01 Mar 2026 05:36:06 +0000 https://status.yeonhong.studio/en#6e2e7572e1e9baff1c414670eeea1f8b3f70d17191a154b4212f2c288bd25d31 KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sun, 01 Mar 2026 05:33:02 +0000 https://status.yeonhong.studio/en#6e2e7572e1e9baff1c414670eeea1f8b3f70d17191a154b4212f2c288bd25d31 KOREA_1 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 KOREA_1 recovered https://status.yeonhong.studio/en Sat, 21 Feb 2026 06:38:59 +0000 https://status.yeonhong.studio/en#72ba27a83e40c419980341a3485183e4b691fa829de5596e03f473ebefd278be KOREA_1 recovered KOREA_1 went down https://status.yeonhong.studio/en Sat, 21 Feb 2026 05:07:10 +0000 https://status.yeonhong.studio/en#72ba27a83e40c419980341a3485183e4b691fa829de5596e03f473ebefd278be KOREA_1 went down KOREA_3 recovered https://status.yeonhong.studio/en Sat, 21 Feb 2026 04:45:37 +0000 https://status.yeonhong.studio/en#f2d7d8cbb8401a71c470fa9446de3759c86a8f3a2daa70569cca6d22850bba64 KOREA_3 recovered KOREA_2 recovered https://status.yeonhong.studio/en Sat, 21 Feb 2026 04:45:09 +0000 https://status.yeonhong.studio/en#83c8390fd3df3eddf0cc26abfb5dc3044ea03692c201f8d8af9c72f88a69f29b KOREA_2 recovered KOREA_3 went down https://status.yeonhong.studio/en Sat, 21 Feb 2026 02:26:01 +0000 https://status.yeonhong.studio/en#f2d7d8cbb8401a71c470fa9446de3759c86a8f3a2daa70569cca6d22850bba64 KOREA_3 went down KOREA_2 went down https://status.yeonhong.studio/en Sat, 21 Feb 2026 02:25:21 +0000 https://status.yeonhong.studio/en#83c8390fd3df3eddf0cc26abfb5dc3044ea03692c201f8d8af9c72f88a69f29b KOREA_2 went down KOREA_2 recovered https://status.yeonhong.studio/en Wed, 18 Feb 2026 12:48:16 +0000 https://status.yeonhong.studio/en#4a64bee5d6bf6bc762273c05bbaaa17bbc928c96a474f960e569ba2858961f6e KOREA_2 recovered KOREA_2 went down https://status.yeonhong.studio/en Wed, 18 Feb 2026 12:46:09 +0000 https://status.yeonhong.studio/en#4a64bee5d6bf6bc762273c05bbaaa17bbc928c96a474f960e569ba2858961f6e KOREA_2 went down Supertone API went down https://status.yeonhong.studio/en Sun, 08 Feb 2026 16:50:56 +0000 https://status.yeonhong.studio/en#0256850ce0c38a3cd1d4f6e120c1407ca2407d86cafb885beaf530b27f8acf3e Supertone API 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 Main TTS API recovered https://status.yeonhong.studio/en Sun, 08 Feb 2026 09:29:26 +0000 https://status.yeonhong.studio/en#ff1003bc5da2c1f4fd7f398a01688466fa75e584ad31ffb1c0342eaa540dd1d9 Main TTS API recovered Main TTS API went down https://status.yeonhong.studio/en Sun, 08 Feb 2026 09:26:19 +0000 https://status.yeonhong.studio/en#ff1003bc5da2c1f4fd7f398a01688466fa75e584ad31ffb1c0342eaa540dd1d9 Main TTS API went down Main TTS API recovered https://status.yeonhong.studio/en Sun, 08 Feb 2026 04:26:21 +0000 https://status.yeonhong.studio/en#db60008e7da8cc9881160ac19cf962a7f2f8c6652331a83b67739a8abc3040ca Main TTS API recovered Main TTS API went down https://status.yeonhong.studio/en Wed, 04 Feb 2026 15:44:19 +0000 https://status.yeonhong.studio/en#db60008e7da8cc9881160ac19cf962a7f2f8c6652331a83b67739a8abc3040ca Main TTS API went down Main TTS API recovered https://status.yeonhong.studio/en Tue, 03 Feb 2026 18:17:26 +0000 https://status.yeonhong.studio/en#d93a53b2ddee9c3b44c83e0814daa94b891e8a261a86da329f5771fd1e023aff Main TTS API recovered Main TTS API went down https://status.yeonhong.studio/en Mon, 02 Feb 2026 16:53:25 +0000 https://status.yeonhong.studio/en#d93a53b2ddee9c3b44c83e0814daa94b891e8a261a86da329f5771fd1e023aff Main TTS API went down Main TTS API recovered https://status.yeonhong.studio/en Mon, 02 Feb 2026 15:32:22 +0000 https://status.yeonhong.studio/en#e17883d7e4c87b683de9c51c27f7ff94f1ed0144080e63cd8b40c9d83650ebed Main TTS API recovered Main TTS API went down https://status.yeonhong.studio/en Wed, 21 Jan 2026 17:02:15 +0000 https://status.yeonhong.studio/en#e17883d7e4c87b683de9c51c27f7ff94f1ed0144080e63cd8b40c9d83650ebed 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 - 점검이 진행될때 목소리 끊김, 메시지를 읽지 않거나 연홍이가 나가지는 문제가 발생할 수 있어요 - 점검 시간은 단축되거나 연장되는 일정 변동이 발생할 수 있어요