- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing, Message Sending
- Regions
- eu, us
- Down Index
- 24of 100
What to do
Check whether you use Customer.io Data Processing, Message Sending in eu, us. 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 32m it lasted.
Anything that failed between 2026-06-10 04:45 UTC and 2026-06-10 05:17 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 4
- investigating
Our team is aware of an issue affecting Customer IO EU and US systems . We are looking into this and gathering more details.
provider
- investigating
Identified the issue, still processing backlog
provider
- monitoring
5% of our customers could have experience delays up to 40minutes, but going forward everything is working correctly
provider
- resolved
This incident has been resolved.
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-e35ac67125
Is Customer.io still down?
No, this incident was resolved 2026-06-10 05:17 UTC. For Customer.io's live state, see https://down.guide/customerio.
How long did it last?
32m, from 2026-06-10 04:45 UTC to 2026-06-10 05:17 UTC, by the times Customer.io posted.
What was affected?
Customer.io named Data Processing, Message Sending in eu, us.
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.