Channel.io Incident History

1. resolvedOct 27 · 09:00 UTC

   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 27, 2026 17:45 ~ 17:51 (KST)
   • Affected Scope: Some customers using the Channelworks web, mobile, and desktop apps, as well as external messenger and app integration services
   • Incident Details:

   1. Some screens in the web, mobile, and desktop apps did not load or responded slowly
   2. Requests from external messengers and app integrations were delayed or returned errors

   • Cause: During an App Store server deployment, the servers handling requests temporarily stopped, causing errors and delays in services connected to the App Store
   • Resolution: The servers have been restored and normal responses have been confirmed. Further deployments have been halted, and the recovery of related services has also been verified.
   • Preventive Measures: We will reorganize the deployment pipeline and strengthen verification to ensure server deployments proceed as intended.

   We apologize for any inconvenience to your use of the service. We will improve our deployment procedures to provide a more stable service.

Reported by Channel.io on their status page.

1. resolvedOct 26 · 19:00 UTC

   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 27, 2026 04:01 ~ 04:09 (KST) (approximately 8 minutes)
   • Affected Scope: Some user chats handled by ALF during the incident, and the ALF settings page
   • Incident Details:

   1. ALF responses were not delivered, or were delayed or cut off, and some chats were transferred to an agent
   2. The ALF settings and preview pages loaded slowly or failed to open

   • Cause: The servers supporting the system experienced a temporary delay in response
   • Resolution: The servers have been restored, and preventive measures will be applied on October 29, 2026 (Thu). Until then, the same issue may recur during early morning hours.

   We will continue to strengthen monitoring to prevent similar issues from occurring again.

Reported by Channel.io on their status page.

1. resolvedOct 23 · 08:50 UTC

   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.

Reported by Channel.io on their status page.