Channelio outage history

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. - Incident Time: October 23, 2026 10:40 ~ 17:50 (KST) (approximately 7 hours 10 minutes) - Affected Scope: In phone consultations received through SKB lines (including 070 numbers issued by SKB), agents heard the customer's voice cutting out. Call connections and lines from other carriers were not affected. - Cause: A network issue on the carrier (SKB) side caused customer audio to arrive delayed and out of order, resulting in parts of the customer's voice being lost. - Resolution: We applied an emergency measure so that delayed audio would not be lost. After SKB completed its recovery at 17:50, the temporary measure was reverted to its original state. We will continue to strengthen monitoring to prevent similar issues from occurring again.

Temporary issue has been detected with CoS 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. - Incident Time: September 23, 2026 16:51:56 ~ September 25, 2026 01:54:00 (KST) (approximately 33 hours 2 minutes) - Affected Scope: Channels that used the Analytics feature during the incident - Incident Details: 1) Some figures were displayed differently from the actual data when viewing customer-related data in Analytics 2) Phone consultation statistics were displayed differently from the actual data 3) Some fields were not displayed in user chat analytics - Cause: During an improvement to the analytics data, an unintended change was applied to a specific component of the system, causing some data to be aggregated and displayed incorrectly. - Resolution: The affected data has been inspected, restored, and corrected. We will continue to strengthen monitoring to prevent similar issues from occurring again.

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.

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 31, 2026 20:00 ~ September 1, 2026 16:00 (KST) (approximately 20 hours) - Affected Scope: Channels using scheduled features such as consultation status changes and follow-up email sending - Incident Details: 1) Scheduled consultation status changes were not processed correctly 2) Follow-up emails were not sent correctly 3) Other scheduled tasks were not processed correctly - Cause: During service improvement work, some servers behaved unintentionally, causing scheduled tasks to be recorded as completed even though they had not actually been processed, which prevented automatic retries. - Resolution: Upon identifying the issue, we took immediate action to ensure tasks are processed correctly, improved the system so tasks are only marked complete once actually finished, and added immediate detection for abnormal server behavior. We will continue to strengthen monitoring to prevent similar issues from occurring again.

Temporary issue has been detected with Marketing 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. - Incident Time: August 31, 2026 20:00 ~ September 1, 2026 16:00 (KST) (approximately 20 hours) - Affected Scope: Channels that sent marketing messages - Incident Details: 1) Campaigns were sent to only some of the intended recipients 2) Some one-time messages (OTMs) failed to send - Cause: During service improvement work, some servers behaved unintentionally, causing scheduled tasks to be recorded as completed even though they had not actually been processed, which prevented automatic retries. - Resolution: Upon identifying the issue, we took immediate action to ensure tasks are processed correctly, improved the system so tasks are only marked complete once actually finished, and added immediate detection for abnormal server behavior. 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.

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.

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.

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.

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.

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 20, 2026 12:00 ~ July 20, 2026 16:00 (KST) (approximately 4 hours) - Affected Scope: Conversations where the automatic chat summary was not generated or was delayed upon closing - Cause: A temporary and significant slowdown in the external AI service used for summary generation caused some summaries to exceed the allowed time limit and be skipped. - Resolution: An emergency fix restored normal operation by 16:00. A structural improvement has since been deployed to run multiple AI models in parallel and use whichever completes first, ensuring summaries are generated normally even if external delays recur. We will continue to strengthen monitoring to prevent similar issues from occurring again. 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.

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. - Incident Time: July 14, 2026 02:00 ~ 10:15 (KST) (approximately 8 hours 15 minutes) - Affected Scope: Some features intermittently did not work properly across the service - Cause: A temporary network connectivity issue caused some requests to be delayed or fail to process. - Resolution: We set a time limit on request processing to prevent delays and carried out stabilization work to prevent related components from restarting unexpectedly. We have also enhanced our monitoring system to detect and respond to similar issues more quickly. 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 Customer Support (Inbox) Snippet 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. - 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.

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.

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.

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.

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.

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.

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)

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.