- Level
- confirmed
- Worst impact
- Degraded
- Components
- Message Sending
- Down Index
- 19of 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 41m it lasted.
Anything that failed between 2026-07-10 17:28 UTC and 2026-07-10 18:08 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
- identified
We're monitoring increased load on our backend that is causing a delay in processing sends. We are actively monitoring the issue and will share updates accordingly.
provider
- monitoring
A fix has been deployed and we are processing through any delay backlogs. We are continuing to monitor but expect delays to reduce shortly.
provider
- resolved
This incident has been resolved and any delays have been fully mitigated.
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-8a13784a3a
Is Customer.io still down?
No, this incident was resolved 2026-07-10 18:08 UTC. For Customer.io's live state, see https://down.guide/customerio.
How long did it last?
41m, from 2026-07-10 17:28 UTC to 2026-07-10 18:08 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.