Skip to main content
Vendor reliability

Vendor record

Customer.io

Vendor reports Operational

Checked

Front door check counts and Customer.io’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against Customer.io in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Customer.io product, region or your app worked.

How we count front door checks

Customer.io says

Incident posts from Customer.io’s status page, with its titles, impact levels and times. They say what Customer.io chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

1

incidents Customer.io posted, last 30 days

All vendors’ incidents

Most recent records · all dates

  • Some customers may experience delays in message sending

    Minor

    Started, per Customer.io

    Closed in our record(34m)

    Customer.io’s post
  • Reduced Deliverability to Microsoft-Hosted Email Addresses

    Not specified

    Started, per Customer.io

    Closed in our record(1h 23m)

    Customer.io’s post
  • Investigating issues with the Agent

    Minor

    Started, per Customer.io

    Closed in our record(5m)

  • Customer.io UI is inaccessible

    Not specified

    Started, per Customer.io

    Closed in our record(34m)

    Customer.io’s post
  • Delays in processing and UI inaccessible for some customers in the US datacentre

    Minor

    Started, per Customer.io

    Closed in our record(27m)

    Customer.io’s post
15 older records
  • Issues accessing EU accounts

    Major

    Started, per Customer.io

    Closed in our record(15m)

    Customer.io’s post
  • Some EU users are experiencing delays in processing

    Minor

    Started, per Customer.io

    Closed in our record(1h 37m)

    Customer.io’s post
  • Some customers are experiencing data processing and message-sending delays

    Minor

    Started, per Customer.io

    Closed in our record(1h 2m)

    Customer.io’s post
  • Delaying in message sending

    Major

    Started, per Customer.io

    Closed in our record(43m)

    Customer.io’s post
  • Some customers are experiencing data processing delays

    Minor

    Started, per Customer.io

    Closed in our record(2h 35m)

    Customer.io’s post
  • Delays processing send events in some environments

    Minor

    Started, per Customer.io

    Closed in our record(42m)

    Customer.io’s post
  • User Interface is currently unavailable for some users in EU. Data processing delays

    Minor

    Started, per Customer.io

    Closed in our record(2h 3m)

    Customer.io’s post
  • User Interface is currently unavailable, data processing delays

    Minor

    Started, per Customer.io

    Closed in our record(33m)

    Customer.io’s post
  • Some customers are currently unable to access the account Billing page in our UI

    Minor

    Started, per Customer.io

    Closed in our record(29m)

    Customer.io’s post
  • Investigating Connectivity Issues

    Major

    Started, per Customer.io

    Closed in our record(2h 42m)

    Customer.io’s post
  • Delays in processing requests

    Minor

    Started, per Customer.io

    Closed in our record(34m)

    Customer.io’s post
  • AI Agent and LLM Campaign Actions Disruption

    Not specified

    Started, per Customer.io

    Closed in our record(1h 12m)

    Customer.io’s post
  • Some customers seeing delays setting up Pipelines in new EU workspaces

    Minor

    Started, per Customer.io

    Closed in our record(52m)

    Customer.io’s post
  • Salesforce and Hubspot syncs might be delayed for some EU customers

    Minor

    Started, per Customer.io

    Closed in our record(1h 29m)

    Customer.io’s post
  • Customer.io UI is currently inaccessible

    Minor

    Started, per Customer.io

    Closed in our record(10m)

    Customer.io’s post

Your code, your dependencies

See which of your code paths call Customer.io

Connect GitHub or GitLab to find where your public or private repository uses Customer.io. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Customer.io status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · Customer.ioStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/customer-io?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Customer.io status badge"></iframe>

Frequently Asked Questions

Is Customer.io currently down?

Customer.io's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Customer.io last have an outage?

The most recent closed incident record began 26 days ago and spans 34 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Customer.io?

No. CheckUpstream does not run front door checks against Customer.io. The incident history on this page is what Customer.io reported, not a measure of how often it was available.

How do I monitor Customer.io in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Customer.io?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.