Customer.io
Customer.io is operational
Issues accessing EU accounts
Customer.io reported that the Management Interface did not work for EU accounts. Customer.io stated that the incident is resolved.
Delays in message sending
Customer.io reports delays in message sending that affect the Message Sending component. Customer.io states that this incident is resolved.
Customer.io UI is currently unavailable for some customers
Customer.io reports that the management interface is unavailable for some customers. Customer.io later reported that the issue is resolved. The outage lasted from 27 October 2026 until 1 November 2026.
Some US customers may experience delays in message sending
Customer.io reports delays in message sending for some customers in the US. The Message Sending component is affected. Customer.io reports that the incident is resolved.
Investigating issues with the Agent
Customer.io reported problems with the Agent. Customer.io later stated that the incident is resolved. The incident started on 3 September 2026 and was resolved on 1 November 2026.
Delays in processing and UI inaccessible for some customers in the US datacentre
Customer.io reports delays in data processing and an inaccessible management interface in the US datacentre. Customer.io states that the incident is resolved. The provider did not give the duration.
Some EU users are experiencing delays in processing
Customer.io reports delays in processing for some users in the EU. The delays affect Data Processing and the Management Interface. Customer.io states that the incident is resolved.
Some customers are experiencing data processing and message-sending delays
Data processing and message sending have delays for some Customer.io customers. Customer.io reports that the incident is resolved and that all backlogs are processed. Customer.io did not give a resolution time.
Reduced Deliverability to Microsoft-Hosted Email Addresses
Message Sending has reduced deliverability to Microsoft-hosted email addresses. Customer.io reports that this issue is resolved. Microsoft resolved the underlying issue, and deliveries to Microsoft services return to normal.
Customer.io UI is inaccessible
The Customer.io Management Interface is inaccessible. Customer.io reports that this incident is resolved.
History
Incidents in 90 days
10
Days with an incident
90
Median duration
No data
Longest incident
No data
Components
7No incident in the last 90 days.
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.
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.cc/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.
https://outages.cc/feed.xml?providers=customerio/feed subscribe https://outages.cc/feed.xml?providers=customerioGo from tracking outages to fixing production issues with Polylane.
Try Polylane