CheckUpstream does not yet run an independent probe against Percy, so no availability figure is published for it — only Percy's own disclosure record below. 1 incident was recorded in the past 12 months; the most recent resolved 138 days ago after 32 minutes. Status signals are polled from Percy'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 Percy yet, so we publish no availability figure for it. What follows is Percy's own disclosure record, which is a different thing.
Percy posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by Percy
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.996%
1y
99.998%
Does Percy actually matter to you?
A Percy 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 →Live Percy status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/percy)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Percy is currently Operational. CheckUpstream tracks Percy 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 Percy down" view? See the Percy Live status page.
Percy's last resolved incident started 138 days ago and lasted 31 minutes (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Percy yet, and the only other figure available would be derived from Percy'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 Percy 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 Percy'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.