Is Channel.io Down?

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. --- [2026-08-07T10:30:38.419+09:00] (investigating) 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.

The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. --- [2026-08-04T20:38:00.066+09:00] (investigating) 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.

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 30, 2026 16:52:16 ~ 17:00:56 (KST) (approximately 9 minutes) - Affected Scope: Some customers using the inbox during the incident - Incident Details: 1) Inbox loading was delayed or did not complete 2) Some additional features and integration calls were not processed normally - Cause: An error occurred in a specific system setting, causing some servers to behave unintentionally, which led to failures in retrieving supplementary inbox data and, in turn, full inbox loading errors. - Resolution: The servers were restored to their previous normal state immediately after the issue was identified, resolving the disruption. We have since added checks to detect immediately when a server is not behaving as intended, and isolated failures in supplementary data retrieval so they no longer affect core inbox functionality. We will continue to strengthen monitoring to prevent similar issues from occurring again. --- [2026-07-31T11:08:59.923+09:00] (investigating) Temporary issue has been detected with Customer Support (Inbox) feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.