- Level
- confirmed
- Worst impact
- Degraded
- Components
- Message Sending
- Down Index
- 18of 100
What to do
Check whether you use Customer.io Message Sending. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 29m it lasted.
Anything that failed between 2026-01-28 18:56 UTC and 2026-01-28 19:26 UTC may need a replay.Subscribe to Customer.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=customerio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Customer.io 3
- investigating
Our engineers are currently investigating an issue where message sending is delayed. We thank you for your patience and will be back with another update as soon as possible.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This issue is now resolved. We greatly appreciate your patience while we investigated.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-3bd782ff18
Is Customer.io still down?
No, this incident was resolved 2026-01-28 19:26 UTC. For Customer.io's live state, see https://down.guide/customerio.
How long did it last?
29m, from 2026-01-28 18:56 UTC to 2026-01-28 19:26 UTC, by the times Customer.io posted.
What was affected?
Customer.io named Message Sending.
What caused it?
Customer.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Customer.io's official status page, https://status.customerio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.