Channel.io Status

All Systems Operational

💬 Live Chat Operational

📞 Meet Operational

📧 Email Operational

🤖 AI ALF Operational

⚡️ Add-ons Operational

🔁 Integration Operational

🗂️ Contacts Operational

🧑‍💻 Customer Support Interface Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Mar 17, 2026

No incidents reported today.

Mar 16, 2026

No incidents reported.

Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

Temporary issue detected with AI ALF feature

Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Issue 1: Response disruption due to Claude model quota exhaustion
- Incident Time: 2026.03.13 11:11 ~ 11:18 (approximately 7 minutes)
- Affected Scope: Some channels using ALF
- Cause: ALF responses were not functioning properly in certain channels due to the exhaustion of the allocated quota for the Claude model.

Issue 2: Service disruption caused by configuration error during model deactivation
- Incident Time: 2026.03.13 11:18 ~ 11:40 (approximately 22 minutes)
- Affected Scope: All channels using the ALF response feature
- Cause: While disabling the Claude model for specific channels to resolve Issue 1, a configuration error caused the model setting to be applied across all channels, resulting in response disruptions.

Issue 3: Response disruption due to Claude model usage control configuration
- Incident Time:2026.03.13 15:16:20 ~ 15:22:50 (KST)
- Affected Scope: Some channels using ALF
- Cause: Due to an issue with the vendor-side control configuration for Claude model calls, ALF responses were not functioning properly in certain channels.

The issue has now been resolved, and the service has been operating normally since 11:40. We sincerely apologize for the inconvenience caused.
Mar 13, 11:18 KST

Temporary issue detected with Phone feature

Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

- Incident Time: March 12, 2026 20:32 ~ March 13, 2026 11:09 (KST)
- Affected Scope: In certain cases where team assignment and VoiceALF were used together in an IVR workflow, calls connected through VoiceALF were not routed to agents when a request to connect to an agent was made.
- Cause: The status change function did not operate correctly when a call waiting for a manager was moved to the queue.
- Resolution: Fixed the issue so that the queue status change function operates correctly.
- Measures to Prevent Recurrence: Strengthen testing across a wider range of environments.
Mar 13, 11:09 KST

Mar 12, 2026

No incidents reported.

Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

Service Partially Unavailable

Resolved - 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. 03. 05 20:18 ~ 2026. 03. 05 20:24 (KST)
- Affected Scope: Connection delays and non-responsiveness on Channel Talk Desk.
- Cause: A sudden surge in database connection demand occurred following improvements to the asynchronous thread pool structure, resulting in a service failure.
- Resolution: Reverted to the previous thread pool structure.
- Measures to Prevent Recurrence: Establish a process to pre-evaluate the impact on DB connections when modifying thread pool structures and strengthen connection-related monitoring alerts.
Mar 5, 20:24 KST

Mar 4, 2026

No incidents reported.

Mar 3, 2026

Temporary issue detected with AI ALF feature

Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

1)
- Incident Time: March 3, 2026 13:20 ~ March 3, 2026 15:22 (KST)
- Affected Scope: ALF knowledge-based responses
- Cause: Temporary resource shortage due to increased Gemini API usage
- Resolution: Temporarily increased the allocated resource quota
- Measures to Prevent Recurrence: Mitigate resource shortages by splitting API calls to distribute load

2)
- Incident Time: March 3, 2026 16:46 ~ March 3, 2026 17:22 (KST)
- Affected Scope: ALF response generation
- Cause: Delay in reflecting stabilization improvements applied to ALF
- Resolution: Switched to an alternative available AI platform
- Measures to Prevent Recurrence: Apply redundancy mechanisms earlier to ensure uninterrupted service in case of ALF-related issues
Mar 3, 18:02 KST

Update - We are continuing to investigate this issue.
Mar 3, 17:12 KST

Investigating - 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.
Mar 3, 17:04 KST