Customer.io UI is currently unavailable for some customers
DegradedOfficial update
0
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.
State
Resolved
Started
5 d ago
2026-10-27 19:11 UTC
Ongoing for
5 days
Worst impact
Degraded
Timeline
1 updateOct 27Oct 29Oct 30Oct 31Nov 2
DegradedUpdate postedDates in UTC
Resolved
5 days 100%
Updates
Times in UTCAs posted by Customer.io
Resolved2026-11-01 17:18 UTC
Thank you for your patience while we investigated; this issue is now resolved.
Affected components
1Management Interface
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.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.
RSS
https://outages.cc/feed.xml?providers=customerioSlack
/feed subscribe https://outages.cc/feed.xml?providers=customerioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane