Skip to content

Outage tracker

CircleCI: the full evidence record

The last 24 hours in detail, 48 days of measured availability, a 12-month summary, our own incident log, CircleCI's declared record, and how the two compare.

← Back to CircleCI's live status

We started measuring CircleCI on August 20, 2026, which is 48 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see CircleCI go down

Measured by our own probes from ten regions, not CircleCI's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what CircleCI's own status page declared. Below it, any public chatter we saw about CircleCI and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what CircleCI's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about CircleCI in the last 24 hours, which is not evidence that nothing is wrong.
CircleCI's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is CircleCI's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention CircleCI next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%2221
US-West100.00%2221
Europe99.95%2219
Asia-Pacific100.00%2197
US-Central100.00%810
Canada100.00%811
UK100.00%811
Southeast Asia100.00%809
Australia100.00%807
South America100.00%811

Monthly summary

Tracking CircleCI since Aug 20, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 20, 2026100%00 min
Sep 2026100%00 min
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for CircleCI: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and CircleCI's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for CircleCI in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: CircleCI's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for CircleCI since we started measuring it on August 20, 2026. We show nothing from before that date.

Their declared record

CircleCI's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Delays starting Gen 2 Docker JobsMinor incident
Oct 1, 2026, 9:06 AM UTC to Oct 1, 2026, 10:45 AM UTC (1h 39m)resolved
their latest update (Oct 1, 2026, 10:45 AM UTC): This incident has been resolved.
Delays in processing new signups and plan changesAll systems operational
Sep 23, 2026, 6:13 PM UTC to Sep 23, 2026, 8:06 PM UTC (1h 53m)resolved
their latest update (Sep 23, 2026, 8:06 PM UTC): This incident has been resolved.
Delays starting Linux Machine jobsMinor incident
Sep 21, 2026, 4:22 PM UTC to Sep 21, 2026, 5:09 PM UTC (47 min)resolved
their latest update (Sep 21, 2026, 5:09 PM UTC): This incident has been resolved.
Customers may experience delays in UI updatesMinor incident
Sep 16, 2026, 2:55 PM UTC to Sep 16, 2026, 7:30 PM UTC (4h 35m)resolved
their latest update (Sep 16, 2026, 7:30 PM UTC): This incident has been resolved.
Customers may experience delays in UI updatesMinor incident
Sep 15, 2026, 2:42 PM UTC to Sep 15, 2026, 5:02 PM UTC (2h 20m)resolved
their latest update (Sep 15, 2026, 5:02 PM UTC): The incident impacting pipeline data in the UI has now been resolved. We thank you for your patience while our engineers worked on reducing the delays.
Increased wait times for macOS jobsMinor incident
Sep 14, 2026, 11:59 AM UTC to Sep 14, 2026, 12:59 PM UTC (1h)resolved
their latest update (Sep 14, 2026, 12:59 PM UTC): Wait times for macOS jobs are back to normal.
Issues loading pipelines for a small number of projectsMinor incident
Sep 10, 2026, 8:25 PM UTC to Sep 10, 2026, 8:26 PM UTC (1 min)resolved
their latest update (Sep 10, 2026, 8:26 PM UTC): This incident has been resolved. A small number of customers who created pipelines between 18:53 UTC and 19:24 UTC that contained config using deprecated config syntax will have seen their build-type jobs fail to start. Customers whose jobs or pipelines failed may rerun them.
macOS Job DelaysMinor incident
Sep 4, 2026, 3:16 PM UTC to Sep 4, 2026, 4:55 PM UTC (1h 40m)resolved
their latest update (Sep 4, 2026, 4:55 PM UTC): We've seen no further impact to queue times and everything has returned to normal. We appreciate your patience while we worked to resolve and monitor this issue.
Intermittent errors when viewing plan usage UIs or calling plan usage APIsMinor incident
Aug 26, 2026, 3:43 PM UTC to Aug 26, 2026, 4:10 PM UTC (27 min)resolved
their latest update (Aug 26, 2026, 4:10 PM UTC): This incident has been resolved.
GitHub Login DisruptionMinor incident
Aug 25, 2026, 11:20 PM UTC to Aug 25, 2026, 8:00 PM UTC (0 min)resolved
their latest update (Aug 25, 2026, 8:00 PM UTC): Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been r…

Showing the 10 most recent of 60 incidents CircleCI has declared in the history we hold.

These entries are CircleCI's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How CircleCI's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording CircleCI's own status page on August 20, 2026, 46 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for CircleCI since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

CircleCI decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If CircleCI believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.