Resolved: Temporary Service Interruption for Subset of EU Customers
Customer.io reports a temporary service interruption for a subset of EU customers. Data Collection, Data Processing, and the Management Interface were affected. Customer.io states that the incident is resolved. The interruption lasted about 9 minutes, from 15:09 to 15:18 UTC.
State
Resolved
Started
Ongoing for
10 h 17 min
Worst impact
Notice
Timeline
1 updateResolved
10 h 17 min 100%
Updates
Times in UTCAs posted by Customer.io
Between 15:09 and 15:18 UTC, a subset of customers in our EU region experienced a brief interruption of service. During this window, API requests may have returned errors, and website data may have been missing, delayed, or incorrect. Webhook delivery was delayed by about 10 minutes. Our infrastructure vendor automatically recycled the faulty hardware, and service was restored automatically afterward. This incident is resolved.
Affected components
3Customer.io in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
90
Median duration
113 days
This incident
100% shorter than the median
Other Customer.io incidents
All incidentsCustomer.io·Customers are Unable to add new Email Sending Domains
Customer.io customers cannot add new Email Sending Domains in the Management Interface. Customer.io reports that the incident is resolved. The incident lasted about 34 minutes.
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.
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.
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.
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.
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.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.
https://outages.live/feed.xml?providers=customerio/feed subscribe https://outages.live/feed.xml?providers=customerioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane