Channel.io Status Page

Aug 7, 2026 · resolved Aug 7

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.

Aug 4, 2026 · resolved Aug 4

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

Jul 30, 2026 · resolved Jul 30

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.

Jul 20, 2026 · resolved Jul 20

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.

Jul 13, 2026 · resolved Jul 13

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.

Is Channel.io down right now?

No — Channel.io is up. All systems operational as of Aug 19, 9:42 PM UTC.

What is Channel.io's current status?

Channel.io: All Systems Operational. Alert24 checks Channel.io's status page continuously and can notify you the moment it changes.

How do I get alerted when Channel.io goes down?

Alert24 monitors Channel.io and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.