CheckUpstream does not yet run an independent probe against Customer.io, so no availability figure is published for it — only Customer.io's own disclosure record below. 28 incidents were recorded in the past 12 months; the most recent resolved 28 days ago after 28 minutes. Status signals are polled from Customer.io's official Atlassian Statuspage status page, alongside independent probes and community reports.
We run no independent probe against Customer.io yet, so we publish no availability figure for it. What follows is Customer.io's own disclosure record, which is a different thing.
Vendor disclosed: 25 incidents · 363 of 365 days with none posted · 2h 1m of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by Customer.io
7d
100.000%
30d
99.997%
90d
99.999%
180d
99.953%
1y
99.977%
Downtime like this can be refundable
If you're a paying Customer.io customer, outages in these windows may count against Customer.io's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A Customer.io outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Time to resolve, from Customer.io's own incident posts (1 year)
Median time to resolve
43m
Slowest 10% take longer than
2h 36m
From 25 incidents Customer.io published and resolved in the last 1 year, measured between their own start and resolution times. It describes how long Customer.io takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is Customer.io currently down?
Customer.io is currently Operational. CheckUpstream tracks Customer.io in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Customer.io's last resolved incident started 28 days ago and lasted 27 minutes (degraded performance).
›What's Customer.io's 30-day uptime?
We don't publish one. CheckUpstream runs no independent probe against Customer.io yet, and the only other figure available would be derived from Customer.io's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
›How do I monitor Customer.io in production?
Sign up to CheckUpstream and add Customer.io to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track Customer.io?
We poll Customer.io's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.