outages.live
Live
Customer.ioIncident · 2026-07-20 21:35 UTC

Some customers are experiencing data processing and message-sending delays

DegradedOfficial update
0

Customer.io reports delays in data processing and message sending for some customers. Customer.io reports that the incident is resolved and that all backlogs are processed. No resolution time is given.

State

Resolved

Started

104 d ago

2026-07-20 21:35 UTC

Ongoing for

104 days

Worst impact

Degraded

Timeline

1 update
Jul 20Aug 15Sep 10Oct 7Nov 2
DegradedUpdate postedDates in UTC

Resolved

104 days 100%

Updates

Times in UTC

As posted by Customer.io

Resolved2026-11-01 20:03 UTC

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

Affected components

2
Data ProcessingMessage Sending

Customer.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

90

Median duration

Not enough data

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

88 days
90 days agoToday

Other Customer.io incidents

All incidents

Customer.io·Customer.io UI is currently unavailable for some customers

The Customer.io Management Interface is unavailable for some customers. Customer.io reports that the issue is resolved. The provider did not state how long the outage lasted.

Degradedupdated 5 d ago

Customer.io·Some US customers may experience delays in message sending

Customer.io reports delays in message sending for some customers in the US. The affected component is Message Sending. Customer.io states that this incident is resolved.

Degradedupdated 43 d ago

Customer.io·Reduced Deliverability to Microsoft-Hosted Email Addresses

Customer.io reports reduced deliverability to Microsoft-hosted email addresses. This affects Message Sending. Customer.io states that Microsoft resolved the underlying issue and deliveries are normal again. Customer.io also states that earlier bounces will be retried.

Noticeupdated 59 d ago

Customer.io·Investigating issues with the Agent

Customer.io reported degraded performance with the Agent. Customer.io later said that the incident is resolved. Customer.io did not give the duration of the incident.

Degradedupdated 59 d ago

Customer.io·Customer.io UI is inaccessible

The Customer.io Management Interface is inaccessible. Customer.io reports that the incident is resolved. Customer.io did not give the outage duration.

Noticeupdated 88 d ago

Follow Customer.io

Your coding agent knows when Customer.io is down, and tells you when a failure is theirs, not yours. You can also get Customer.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "customerio" and tell me if Customer.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=customerio
Slack
/feed subscribe https://outages.live/feed.xml?providers=customerio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane