Skip to main content
Customer.io

Some customers are experiencing data processing and message-sending delays

Degraded Lasted 1h 23m · started · Customer.io's page

Level
confirmed
Worst impact
Degraded
Components
Data Processing, Message Sending
Regions
us
Down Index
23of 100

What to do

  • Check whether you use Customer.io Data Processing, Message Sending in 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 1h 23m it lasted.

    Anything that failed between 2026-07-20 21:35 UTC and 2026-07-20 22:58 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

  1. investigating

    Our engineers are currently looking into an issue that is causing data processing and message-sending delays for a small subset of customers in the US region. We apologise for any inconvenience caused.

    provider

  2. identified

    The issue has been identified and we're working on a fix. Thank you for your patience.

    provider

  3. monitoring

    A fix has been deployed, and we are processing any delayed backlogs. We are continuing to monitor the results.

    provider

  4. resolved

    This incident has been resolved and all backlogs have been processed.

    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-d85ff0d9fd

Is Customer.io still down?

No, this incident was resolved 2026-07-20 22:58 UTC. For Customer.io's live state, see https://down.guide/customerio.

How long did it last?

1h 23m, from 2026-07-20 21:35 UTC to 2026-07-20 22:58 UTC, by the times Customer.io posted.

What was affected?

Customer.io named Data Processing, Message Sending in 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.