Historial de interrupciones de Channelio

1. 1 de septiembre de 2026 a las 6:02 UTCinvestigating

   Se ha detectado un problema temporal con la función Atención al Cliente (Inbox). Actualmente estamos investigando la causa y proporcionaremos actualizaciones en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar.

2. 1 de septiembre de 2026 a las 7:37 UTCresolved

   Se ha resuelto la cuestión temporal y el servicio está en pleno funcionamiento. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. - Hora del incidente: 31 de agosto de 2026 20:00 ~ 1 de septiembre de 2026 16:00 (KST) (aproximadamente 20 horas) - Ámbito Afectado: Canales usando funciones programadas como cambios de estado de consulta y correo electrónico de seguimiento - Detalles del incidente: 1) No se procesaron correctamente los cambios previstos en el estado de las consultas 2) Los correos electrónicos de seguimiento no fueron enviados correctamente 3) Otras tareas programadas no se tramitaron correctamente - Causa: Durante el trabajo de mejora del servicio, algunos servidores se comportaron involuntariamente, causando que las tareas programadas se registraran como terminadas aunque no se hubieran procesado realmente, lo que impidió las retries automáticas. - Resolución: Al identificar el problema, tomamos medidas inmediatas para asegurar que las tareas sean procesadas correctamente, mejoramos el sistema así que las tareas sólo están marcadas completas una vez terminadas, y agregamos detección inmediata para el comportamiento anormal del servidor. Seguiremos fortaleciendo la vigilancia para evitar que vuelvan a ocurrir cuestiones similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. 1 de septiembre de 2026 a las 5:02 UTCinvestigating

   Se ha detectado un problema temporal con la función Marketing. Actualmente estamos investigando la causa y proporcionaremos actualizaciones en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar.

2. 1 de septiembre de 2026 a las 7:37 UTCresolved

   Se ha resuelto la cuestión temporal y el servicio está en pleno funcionamiento. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. - Hora del incidente: 31 de agosto de 2026 20:00 ~ 1 de septiembre de 2026 16:00 (KST) (aproximadamente 20 horas) - Ámbito afectado: Canales que enviaron mensajes de marketing - Detalles del incidente: 1) Se enviaron campañas a algunos de los destinatarios previstos 2) Algunos mensajes de una sola vez (OTMs) no enviaron - Causa: Durante el trabajo de mejora del servicio, algunos servidores se comportaron involuntariamente, causando que las tareas programadas se registraran como terminadas aunque no se hubieran procesado realmente, lo que impidió las retries automáticas. - Resolución: Al identificar el problema, tomamos medidas inmediatas para asegurar que las tareas sean procesadas correctamente, mejoramos el sistema así que las tareas sólo están marcadas completas una vez terminadas, y agregamos detección inmediata para el comportamiento anormal del servidor. Seguiremos fortaleciendo la vigilancia para evitar que vuelvan a ocurrir cuestiones similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de agosto de 2026 a las 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. 7 de agosto de 2026 a las 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. 4 de agosto de 2026 a las 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. 4 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de julio de 2026 a las 8:02 UTCinvestigating

   Se ha detectado un problema temporal con la función Atención al Cliente (Inbox). Actualmente estamos investigando la causa y proporcionaremos actualizaciones en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar.

2. 30 de julio de 2026 a las 8:04 UTCresolved

   Se ha resuelto la cuestión temporal y el servicio está en pleno funcionamiento. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. - Tiempo de incidentes: 30 de julio de 2026 16:52:16 ~ 17:00:56 (KST) (aproximadamente 9 minutos) - Ámbito Afectado: Algunos clientes usando la bandeja de entrada durante el incidente - Detalles del incidente: 1) La carga de la caja se atrasó o no terminó 2) Algunas características adicionales y llamadas de integración no se procesaron normalmente - Causa: Se produjo un error en un sistema específico, causando que algunos servidores se comportaran involuntariamente, lo que dio lugar a fallos en la recuperación de datos complementarios de la caja y, a su vez, errores de carga de la caja completa. Resolución: Los servidores fueron restaurados a su estado normal anterior inmediatamente después de que se identificó el problema, resolviendo la interrupción. Desde entonces hemos añadido cheques para detectar inmediatamente cuando un servidor no se comporta como se desea, y fallas aisladas en la recuperación de datos suplementarios para que ya no afecten la funcionalidad de la caja central. Seguiremos fortaleciendo la vigilancia para evitar que vuelvan a ocurrir cuestiones similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de julio de 2026 a las 3:06 UTCresolved

   Se ha resuelto la cuestión temporal y el servicio está en pleno funcionamiento. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. - Hora del incidente: 20 de julio de 2026 12:00 ~ 20 de julio de 2026 16:00 (KST) (aproximadamente 4 horas) - Ámbito Afectado: Conversaciones donde el resumen automático de chat no se generó o se retrasó al cerrar - Causa: Una desaceleración temporal y significativa en el servicio exterior de IA utilizado para la generación de sumarios causó que algunos resúmenes superaran el límite de tiempo permitido y fueran saltados. Resolución: Una solución de emergencia restaurada operación normal a las 16:00. Desde entonces se ha implementado una mejora estructural para ejecutar múltiples modelos de IA en paralelo y utilizar los que se completan primero, asegurando que los resúmenes se generen normalmente incluso si se repiten retrasos externos. Seguiremos fortaleciendo la vigilancia para evitar que vuelvan a ocurrir cuestiones similares. Se ha detectado un problema temporal con la función Atención al Cliente (Inbox). Actualmente estamos investigando la causa y proporcionaremos actualizaciones en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar.

Traducido automáticamente desde la actualización oficial del incidente.

1. 27 de julio de 2026 a las 9:05 UTCresolved

   Se ha detectado un problema temporal con la función Atención al Cliente (Inbox). Actualmente estamos investigando la causa y proporcionaremos actualizaciones en breve. Nos disculpamos por cualquier inconveniente que esto pueda causar. - Hora del incidente: 14 de julio de 2026 02:00 ~ 10:15 (KST) (aproximadamente 8 horas 15 minutos) - Ámbito afectado: Algunas características intermitentemente no funcionaron correctamente en todo el servicio - Causa: Un problema de conectividad de red temporal causó que algunas solicitudes se retrasaran o no se procesaran. Resolución: Se establece un límite de tiempo para el procesamiento de solicitudes para evitar demoras y realizar trabajos de estabilización para evitar que los componentes relacionados reanuden inesperadamente. También hemos mejorado nuestro sistema de vigilancia para detectar y responder con mayor rapidez a cuestiones similares. Se ha resuelto la cuestión temporal y el servicio está en pleno funcionamiento. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 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. 13 de julio de 2026 a las 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. 24 de junio de 2026 a las 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. 23 de junio de 2026 a las 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. 23 de junio de 2026 a las 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. 22 de junio de 2026 a las 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. 22 de junio de 2026 a las 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. 5 de junio de 2026 a las 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. 26 de mayo de 2026 a las 2:41 UTCmonitoring

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

2. 26 de mayo de 2026 a las 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. 26 de mayo de 2026 a las 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. 21 de mayo de 2026 a las 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. 21 de mayo de 2026 a las 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. 21 de mayo de 2026 a las 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. 18 de mayo de 2026 a las 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. 18 de mayo de 2026 a las 2:06 UTCmonitoring

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

3. 18 de mayo de 2026 a las 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. 14 de mayo de 2026 a las 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. 14 de mayo de 2026 a las 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. 14 de mayo de 2026 a las 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. 4 de mayo de 2026 a las 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. 27 de abril de 2026 a las 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. 28 de abril de 2026 a las 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. 24 de abril de 2026 a las 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. 24 de abril de 2026 a las 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. 23 de abril de 2026 a las 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. 23 de abril de 2026 a las 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.