Channelio 中断历史

1. 2026年9月1日 UTC 06:02investigating

   通过客户支持(Inbox)功能检测出临时发行. 我们目前正在调查这一原因,不久将提供最新情况。 我们对此可能造成的不便表示歉意.

2. 2026年9月1日 UTC 07:37resolved

   临时问题已经解决,服务现已全面开通. 我们对此可能造成的不便表示歉意。 - 事件时间:2026年8月31日 20:00~9月1日 20:26 16:00 (KST)(约20小时) - 受影响范围:利用预定功能的频道,如咨询状况变化和后续电子邮件发送 - 事件细节: (1) 计划的协商地位变化没有得到正确处理 (2) 后续电子邮件发送不当 3) 其他预定任务处理不当 - 原因:在服务改进工作期间,有些服务器行为不慎,导致预定任务记录为已完成,尽管这些任务实际上没有得到处理,因而无法自动重复。 - 决议:在查明问题后,我们立即采取行动,确保正确处理各项任务,改进系统,使各项任务只在实际完成后才被标记完成,并增加了对服务器异常行为的即时检测。 我们将继续加强监测,防止类似问题再次发生.

自动翻译自官方事件更新。

1. 2026年9月1日 UTC 05:02investigating

   发现带有营销特性的临时问题。 我们目前正在调查这一原因,不久将提供最新情况。 我们对此可能造成的不便表示歉意.

2. 2026年9月1日 UTC 07:37resolved

   临时问题已经解决,服务现已全面开通. 我们对此可能造成的不便表示歉意。 - 事件时间:2026年8月31日 20:00~9月1日 20:26 16:00 (KST)(约20小时) - 受影响范围:发送营销信息的渠道 - 事件细节: (1) 运动只发给一些预定接受者 (2) 一些一次性信件( OTM) 发送失败 - 原因:在服务改进工作期间,有些服务器行为不慎,导致预定任务记录为已完成,尽管这些任务实际上没有得到处理,因而无法自动重复。 - 决议:在查明问题后,我们立即采取行动,确保正确处理各项任务,改进系统,使各项任务只在实际完成后才被标记完成,并增加了对服务器异常行为的即时检测。 我们将继续加强监测,防止类似问题再次发生.

自动翻译自官方事件更新。

1. 2026年8月7日 UTC 01:30investigating

   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日 UTC 01:41resolved

   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日 UTC 11:34investigating

   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日 UTC 23:22resolved

   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日 UTC 08:02investigating

   通过客户支持(Inbox)功能检测出临时发行. 我们目前正在调查这一原因,不久将提供最新情况。 我们对此可能造成的不便表示歉意.

2. 2026年7月30日 UTC 08:04resolved

   临时问题已经解决,服务现已全面开通. 我们对此可能造成的不便表示歉意。 - 事件时间:2026年7月30日 16:52:16~17:00:56(KST)(约9分钟) - 受影响范围:事件期间一些客户使用收件箱 - 事件细节: 1) 收件箱装载被延迟或未完成 2) 某些附加功能和整合电话没有正常处理 - 原因:在特定的系统设置中发生了错误,导致一些服务器无意地行为,导致无法检索补充收件箱数据,进而无法完全收件箱装入错误。 - 决议:在查明问题后,服务器立即恢复到以前的正常状态,解决了中断问题。 自此之后,我们增加了检查,以便立即发现服务器未按预期行事的情况,以及补充数据检索方面的个别故障,从而不再影响核心收件箱功能。 我们将继续加强监测,防止类似问题再次发生.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 03:06resolved

   临时问题已经解决,服务现已全面开通. 我们对此可能造成的不便表示歉意。 - 事件时间:2026年7月20日 中午12:00~2026年7月20日 4:00(KST)(约4小时) - 受影响范围:在自动聊天摘要未生成或关闭时被延迟的情况下进行的对话 - 原因:用于摘要生成的外部AI服务暂时大幅放缓,导致一些摘要超过允许的时限被跳过。 - 解析:16:00前恢复了应急装置的正常运行。 从那时起,已进行结构改进,以平行运行多个AI模型,并使用最先完成者,确保即使外部延迟再次发生,通常也能生成摘要。 我们将继续加强监测,防止类似问题再次发生。 通过客户支持(Inbox)功能检测出临时发行. 我们目前正在调查这一原因,不久将提供最新情况。 我们对此可能造成的不便表示歉意.

自动翻译自官方事件更新。

1. 2026年7月27日 UTC 09:05resolved

   通过客户支持(Inbox)功能检测出临时发行. 我们目前正在调查这一原因,不久将提供最新情况。 我们对此可能造成的不便表示歉意。 - 事件发生时间:2026年7月14日02:00~10:15(KST)(约8小时15分) - 受影响范围:有些特征断断续续地没有在整个服务中适当发挥作用 - 原因:一个临时的网络连接问题导致一些请求被推迟或未能处理。 - 决议:我们规定了处理请求的时限,以防止拖延,并开展稳定工作,防止有关部件意外地重新启动。 我们还加强了我们的监测系统,以更快地发现和应对类似问题。 临时问题已经解决,服务现已全面开通. 我们对此可能造成的不便表示歉意.

自动翻译自官方事件更新。

1. 2026年7月10日 UTC 04:22investigating

   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日 UTC 06:20resolved

   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日 UTC 13:00resolved

   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日 UTC 07:11investigating

   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日 UTC 08:16resolved

   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日 UTC 06:15investigating

   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日 UTC 06:19resolved

   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日 UTC 05:49resolved

   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日 UTC 02:41monitoring

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

2. 2026年5月26日 UTC 06:36investigating

   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日 UTC 06:37resolved

   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日 UTC 11:55monitoring

   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日 UTC 12:08investigating

   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日 UTC 13:02resolved

   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日 UTC 01:32investigating

   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日 UTC 02:06monitoring

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

3. 2026年5月18日 UTC 02:37resolved

   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日 UTC 10:49investigating

   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日 UTC 10:56monitoring

   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日 UTC 11:22resolved

   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日 UTC 08:56resolved

   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日 UTC 08:50investigating

   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日 UTC 06:19resolved

   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日 UTC 00:39investigating

   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日 UTC 02:11resolved

   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日 UTC 02:23investigating

   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日 UTC 03:29resolved

   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.