Channelio の障害履歴

1. 2026年9月1日 6:02 UTCinvestigating

   カスタマーサポート(Inbox)機能で一時的な問題が検出されました。 現在、原因を調査し、早期に更新を行います。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年9月1日 7:37 UTCresolved

   一時的な問題が解決され、サービスが完全に運用されています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ・出勤時間:8月31日(土)、2026日(日)20:00～9月1日(日)2026 16:00(KST)(約20時間) - 感染したスコープ:相談状況変更やフォローアップメール送信などのスケジュール機能を使用したチャネル - インシデントの詳細: 1) 相談状況変更が正しく処理されていない 2) フォローアップメールが正しく送信されていない 3)その他のスケジュールされたタスクは正しく処理されていない - 原因:サービス改善作業中に、一部のサーバーは意図せずに振る舞い、実際に処理されていないにもかかわらず、スケジュールされたタスクが完成するようにしました。 - 解像度:問題を特定すると、タスクが正しく処理されるように、システムが改善されるため、タスクが実際に終了したら完全にマークされ、異常なサーバーの動作に対する即時検出が追加されました。 今後も同様の問題が起きるのを防ぐため、モニタリングを強化してまいります.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月1日 5:02 UTCinvestigating

   マーケティング機能で一時的な問題が検出されました。 現在、原因を調査し、早期に更新を行います。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年9月1日 7:37 UTCresolved

   一時的な問題が解決され、サービスが完全に運用されています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ・出勤時間:8月31日(土)、2026日(日)20:00～9月1日(日)2026 16:00(KST)(約20時間) - 感染したスコープ:マーケティングメッセージを送信するチャネル - インシデントの詳細: 1) 目的の受取人のみにキャンペーンを送信 2) 送信に失敗したワンタイムメッセージ(OTM) - 原因:サービス改善作業中に、一部のサーバーは意図せずに振る舞い、実際に処理されていないにもかかわらず、スケジュールされたタスクが完成するようにしました。 - 解像度:問題を特定すると、タスクが正しく処理されるように、システムが改善されるため、タスクが実際に終了したら完全にマークされ、異常なサーバーの動作に対する即時検出が追加されました。 今後も同様の問題が起きるのを防ぐため、モニタリングを強化してまいります.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月7日 1:30 UTCinvestigating

   Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年8月7日 1:41 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: August 6, 2026 19:30 ~ August 7, 2026 10:32 (KST) (approximately 15 hours 2 minutes) - Affected Scope: 154 calls across 10 channels, occurring only in calls where an agent was connected after ALF Phone Support responded first - Cause: A change in a specific processing logic of the system caused voice not to connect when a call was transferred to an agent after ALF Phone Support had responded first. - Resolution: The affected logic has been restored to its previous state, and we plan to ensure voice connects properly every time a call is transferred to an agent. Test cases for agent handoff and call transfers in ALF Phone Support have also been added to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again.

1. 2026年8月4日 11:34 UTCinvestigating

   CoS and Notebook are temporarily unavailable exclusively for data provided by default in Channel Talk. As a result, CoS and Notebook features using data such as user, userchat, events, and manager, as well as orders, cart_items, and products data from the Cafe24 app, are not functioning properly. - Notebooks already built with the relevant data will only display data prior to 8:00 PM UTC+9. - Default consultation statistics, Custom Reports, and CoS/Notebook analyses using custom-integrated data are unaffected. - Cafe24 app functions and task executions are also unaffected. - We will provide further notice upon completion of maintenance. We sincerely apologize for the inconvenience.

2. 2026年8月4日 23:22 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

1. 2026年7月30日 8:02 UTCinvestigating

   カスタマーサポート(Inbox)機能で一時的な問題が検出されました。 現在、原因を調査し、早期に更新を行います。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

2. 2026年7月30日 8:04 UTCresolved

   一時的な問題が解決され、サービスが完全に運用されています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ・出勤時間:7月30日、2026日 16:52:16～17:00:56(KST)(約9分) - 感染したスコープ:インシデント中に受信トレイを使用しているお客様 - インシデントの詳細: 1) 箱のローディングは遅れていましたりまたは完了しなかった 2) いくつかの追加機能と統合コールが正常に処理されていない - 原因: エラーは、特定のシステム設定で発生しました。, 意図せずに動作するためにいくつかのサーバーを引き起こします, サプリメントの受信トレイのデータを取得するの失敗につながり、, 順番に, 完全な受信トレイの読み込みエラー. - 解像度: 問題が特定された直後にサーバーは以前の正常な状態に復元され、混乱を解決しました。 サーバが意図どおりに動揺されていないとき、サーバーがすぐに検出するチェックを追加し、補完的なデータ検索で分離された障害が発生し、コアの受信トレイの機能には影響しません。 今後も同様の問題が起きるのを防ぐため、モニタリングを強化してまいります.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月21日 3:06 UTCresolved

   一時的な問題が解決され、サービスが完全に運用されています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ・出勤時間:7月20日(水)12:00～7月20日(金)16時(予定) - 感染したスコープ:自動チャットの要約が生成されなかったり、終了時に遅延した会話 - 原因: 要約生成に使用される外部AIサービスの一時的かつ重要な減速は、許された時間制限を超えてスキップするいくつかの要約を引き起こしました。 - 決断:緊急事態は16:00までに正常な操作を元通りにしました。 構造的改善は、複数のAIモデルを並行して実行し、最初に完了する使用するためにデプロイされたので、外部遅延が再発しても、要約が正常に生成されることを保証します。 今後も同様の問題が起きるのを防ぐため、モニタリングを強化してまいります。 カスタマーサポート(Inbox)機能で一時的な問題が検出されました。 現在、原因を調査し、早期に更新を行います。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月27日 9:05 UTCresolved

   カスタマーサポート(Inbox)機能で一時的な問題が検出されました。 現在、原因を調査し、早期に更新を行います。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ・出勤時間:7月14日、2026日02:00～10:15(KST)(約8時間15分) - 感染したスコープ: 断続的にサービス全体で正常に動作しなかったいくつかの機能 - 原因:一時的なネットワーク接続の問題は、遅延またはプロセスに失敗する要求を引き起こしました。 - 解像度: 遅延を防止し、関連するコンポーネントが予期しない再起動を防止するために安定化作業を実施するために、処理に制限時間を設定します。 また、モニタリングシステムを強化し、類似の問題をより迅速に検知・対応しています。 一時的な問題が解決され、サービスが完全に運用されています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月10日 4:22 UTCinvestigating

   Temporary issue has been detected with Customer Support (Inbox) Snippet feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年7月13日 6:20 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: July 10, 2026 04:47 ~ 14:31 (KST) (approximately 9 hours 44 minutes) - Affected Scope: Channels using snippets - Cause: A styling issue caused dropdown and snippet colors to not display correctly. - Resolution: The system was restored to its previous state and the root cause has been fixed. Pre-release checks will be strengthened to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again.

1. 2026年6月24日 13:00 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: June 24, 2026 20:48 ~ 21:23 (KST) (approximately 35 minutes) - Affected Scope: Phone feature (inbound/outbound calls) - Cause: A change in the internal data structure caused the Meet feature to stop functioning properly. - Resolution: The system has been restored to its previous state, and we will be improving our deployment process to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again. Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

1. 2026年6月23日 7:11 UTCinvestigating

   Temporary issue has been detected with Kakao Talk Integration Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年6月23日 8:16 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: June 23, 2026 15:00 ~ 17:00 (KST) (approximately 2 hours) - Affected Scope: File and image messages sent by customers via KakaoTalk. - Cause: File and image messages were not properly received due to a Kakao service outage. - Resolution: The service was restored following the recovery of Kakao's service outage.

1. 2026年6月22日 6:15 UTCinvestigating

   Channel Talk system is experiencing an issue. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年6月22日 6:19 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: June 22, 2026 14:50 ~ 15:15 (KST) (approximately 25 minutes) - Affected Scope: All channels accessing the Channel Talk app and pages - Cause: An error occurred upon access due to a display configuration issue within the admin app. - Resolution: The affected configuration has been corrected and the service has been restored.

1. 2026年6月5日 5:49 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. Temporary issue has been detected with AI ALF feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause. - Incident Time: June 5, 2026 14:34:45 ~ 14:38:30 (KST)

1. 2026年5月26日 2:41 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

2. 2026年5月26日 6:36 UTCinvestigating

   Temporary issue has been detected with SMS Sending Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

3. 2026年5月26日 6:37 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 24, 2026 04:00 ~ May 26, 2026 10:50 (KST) (approximately 2 days 6 hours 50 minutes) - Affected Scope: Domestic SMS sending via the marketing and follow-up notification features - Cause: During an internal system maintenance, SMS processing was not resumed, resulting in a failure to deliver text messages. - Resolution: SMS processing has been resumed and the service has been restored. Two-stage monitoring has been added to prevent recurrence.

1. 2026年5月21日 11:55 UTCmonitoring

   We have identified the cause of the current outage and have taken corrective action. We are currently monitoring the service for stabilization. We will provide you with an update as soon as we confirm the detailed cause. We apologize for any inconvenience this may have caused.

2. 2026年5月21日 12:08 UTCinvestigating

   Temporary issue has been detected with Kakao Talk Integration Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

3. 2026年5月21日 13:02 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 21, 2026 19:00 ~ 22:00 (KST) (approximately 3 hours) - Affected Scope: Channels using messaging integrations (KakaoTalk, WeChat, etc.) and shopping mall integrations (GodoMall, ShopBy, etc.) - Incident Details: 1) Messages could not be sent through messaging apps such as KakaoTalk and WeChat 2) Order information was not saved for integrated shopping malls such as Godo Mall and ShopBy - Cause: A compatibility issue between some servers occurred during a system update. - Resolution: The affected servers were updated to restore compatibility and resolve the issue.

1. 2026年5月18日 1:32 UTCinvestigating

   Channel Talk system is experiencing an issue. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年5月18日 2:06 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年5月18日 2:37 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 18, 2026 10:03 ~ 11:14 (KST) (approximately 71 minutes) - Affected Scope: Delays in inbox loading, IVR response, and App Store settings screen access in some environments during the incident period - Cause: Repeated data lookup requests in App Store-related features caused a temporary surge in load on the server managing the data, which also delayed other requests using the same server. - Resolution: The processing path causing the load was temporarily disabled to restore service. Going forward, the affected processing will be separated into its own flow, and frequently used information will be stored in advance for faster access. We have also adjusted request volume and processing time to prevent similar load from accumulating again. We will continue to strengthen monitoring to prevent similar issues from occurring again.

1. 2026年5月14日 10:49 UTCinvestigating

   Channel Talk system is experiencing an issue. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年5月14日 10:56 UTCmonitoring

   We have identified the cause of the current outage and have taken corrective action. We are currently monitoring the service for stabilization. We will provide you with an update as soon as we confirm the detailed cause. We apologize for any inconvenience this may have caused.

3. 2026年5月14日 11:22 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. Incident Time: May 14, 2026, 19:47 – 20:03 (KST) Scope of Impact: Temporary unavailability of the Channel Talk admin application, including disruptions to auto-assignment and agent status updates. Cause: Temporary system overload during a deployment for product improvements. Resolution: Resolved the overload by scaling up the database servers and performing a rollback.

1. 2026年5月4日 8:56 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 4, 2026 09:59 ~ 13:17 (KST) (approximately 3 hours 18 minutes) - Affected Scope: Intermittent delays and failures in customer contact lookups and marketing recipient lookups in some channels during the incident period - Cause: Load was concentrated on some servers handling data, causing temporary delays and intermittent failures - Resolution: Initial load balancing has been completed, and additional stabilization work will follow. Temporary issue has been detected with Contacts feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

1. 2026年4月27日 8:50 UTCinvestigating

   Temporary issue has been detected with AI ALF Statistics feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年4月28日 6:19 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: April 24, 2026 15:00 ~ April 27, 2026 23:50 (KST) (approximately 3 days 8 hours 50 minutes) - Affected Scope: Channels provided with the renewed ALF analytics feature - Cause: Data from some periods was omitted from aggregation, resulting in inaccurate results being displayed - Resolution: Aggregation has been corrected to include all previously omitted data from the affected periods.

1. 2026年4月24日 0:39 UTCinvestigating

   We are currently experiencing a temporary issue with the Channel Talk service. We have identified an issue where users are unable to log in on Android mobile devices after a new login or logging out. We are urgently investigating the cause and will provide updates as soon as possible. We sincerely apologize for any inconvenience this may cause.

2. 2026年4月24日 2:11 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time: 2026-04-23 19:44 ~ 2026-04-24 11:05 (KST) -Affected Scope: Users who launched the Android app while in a logged-out state. -Cause: Following a server update, an issue occurred where the app entered an unexpected path during the launch process while not logged in. -Resolution: Reverted the server to its previous state and updated the Android app. -Measures to Prevent Recurrence: Strengthen pre-deployment testing for scenarios that could cause the app to freeze or hang during the launch process.

1. 2026年4月23日 2:23 UTCinvestigating

   Temporary issue has been detected with AI ALF feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. 2026年4月23日 3:29 UTCresolved

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: April 22, 2026 21:30 ~ April 23, 2026 12:00 (KST) (approximately 14 hours 30 minutes) - Affected Scope: User chats newly created during the incident in which tasks were triggered - Cause: A temporary disruption occurred after a change in a specific processing logic of the system - Resolution: The affected logic has been rolled back, and internal inspection procedures have been strengthened to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again.