CheckUpstream measured CircleCI at 99.929% availability across 2827 independent checks (global · api). 43 incidents were recorded in the past 12 months; the most recent resolved 5 days ago after 27 minutes. Status signals are polled from CircleCI's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
99.929%
global · api · n=2827 · p95 280ms (30d)
Share of our own checks against CircleCI endpoints that returned CircleCI's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 8 incidents · 29 of 30 days with none posted · 3h 55m of declared impact
Fewer incidents in the last 30 days than 12% of 232 tracked services.
Share of each window with no impact declared by CircleCI
7d
99.920%
30d
99.455%
90d
99.818%
180d
99.692%
1y
99.848%
Downtime like this can be refundable
If you're a paying CircleCI customer, outages in these windows may count against CircleCI'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 CircleCI entitlement →Does CircleCI actually matter to you?
A CircleCI 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 8 incidents CircleCI published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long CircleCI takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 26, 15:43 UTC · resolved in 6m · Resolved
Aug 26, 15:43 UTC · resolved in 26m · Resolved
Aug 17, 21:06 UTC · resolved in 34m · Resolved
Live CircleCI status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/circleci)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
CircleCI is currently Operational. CheckUpstream tracks CircleCI in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
CircleCI's last resolved incident started 5 days ago and lasted 26 minutes (degraded performance).
Looking for the live "is CircleCI down" view? See the CircleCI Live status page.
Aug 17, 14:04 UTC · resolved in 5h 5m · Resolved
Jul 20, 00:35 UTC · resolved in 2h 29m · Resolved
Jul 16, 23:04 UTC · resolved in 1h 26m · Resolved
Jul 14, 22:54 UTC · resolved in 1h 45m · Resolved
Jul 14, 02:49 UTC · resolved in 2h 35m · Resolved
Jul 13, 21:52 UTC · resolved in 1d 1h · Resolved
Jul 13, 18:55 UTC · resolved in 54m · Resolved
Jul 2, 15:25 UTC · resolved in 1h 20m · Resolved
Jun 29, 10:23 UTC · resolved in 6h 42m · Resolved
Jun 25, 22:44 UTC · resolved in 21m · Resolved
Jun 24, 23:13 UTC · resolved in 3h 58m · Resolved
CircleCI's 30-day measured availability is 99.929%, from CheckUpstream's own probes against CircleCI endpoints. It is the share of checks that returned the expected response, not a figure taken from CircleCI's status page.
Sign up to CheckUpstream and add CircleCI 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 CircleCI'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.