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.
Independent measurement how this is computed
Not measured
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: 16 incidents · 90 of 90 days with none posted · 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.
Track your Customer.io entitlement →Does Customer.io actually matter to you?
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.
Check a repository →From 16 incidents Customer.io published and resolved in the last 90 days, 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.
Aug 3, 07:20 UTC · resolved in 4m · Resolved
Aug 3, 07:17 UTC · resolved in 27m · Resolved
Jul 31, 14:24 UTC · resolved in 15m · Resolved
Live Customer.io status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/customer-io)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
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.
Looking for the live "is Customer.io down" view? See the Customer.io Live status page.
Jul 23, 08:27 UTC · resolved in 1h 37m · Resolved
Jun 18, 20:06 UTC · resolved in 29m · Resolved
Jun 13, 21:18 UTC · resolved in 2h 42m · Resolved
Jun 10, 04:45 UTC · resolved in 34m · Resolved
Jun 5, 12:57 UTC · resolved in 52m · Resolved
Jun 4, 23:50 UTC · resolved in 1h 29m · Resolved
Jun 4, 13:34 UTC · resolved in 10m · Resolved
Jun 2, 21:18 UTC · resolved in 1h 43m · Resolved
Jun 1, 11:40 UTC · resolved in 40m · Resolved
May 29, 16:26 UTC · resolved in 43m · Resolved
May 25, 15:27 UTC · resolved in 52m · Resolved
Customer.io's last resolved incident started 28 days ago and lasted 27 minutes (degraded performance).
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.
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).
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.