- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 100
What to do
Check whether your product depends on Customer.io. 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 11m it lasted.
Anything that failed between 2026-01-21 20:45 UTC and 2026-01-21 20:55 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 2
- identified
Our team is aware of and has identified an issue that is causing our App API to return a 500 error when attempting to download custom exports. We're working on getting a resolution in place, and appreciate your patience.
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-cb42bc0908
Is Customer.io still down?
No, this incident was resolved 2026-01-21 20:55 UTC. For Customer.io's live state, see https://down.guide/customerio.
How long did it last?
11m, from 2026-01-21 20:45 UTC to 2026-01-21 20:55 UTC, by the times Customer.io posted.
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.