Channel.io Incident History

Operational

channel.io ↗9 components

checked Sep 11, 2026 11:31 AM UTC · Channel.io's official status page

Channel.io is up and running.

Channel.io is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.

Channel.io status

Be the first to know

Statusfield watches Channel.io alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

Channel.io incident history

2 reports published by Channel.io in the last 30 days

When Channel.io breaks, it is typically resolved in 1h 52m — median across 4 resolved incidents over 90 days.

September 1, 2026

Temporary issue detected with Marketing feature

Last update Sep 1, 2026 · 08:46 UTC

resolvedSep 1 · 07: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: 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.

Reported by Channel.io on their status page.

Temporary issue detected with Customer Support (Inbox)

Last update Sep 1, 2026 · 08:40 UTC

resolvedSep 1 · 07:37 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: 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.

Reported by Channel.io on their status page.