Skip to content

Outage tracker / CircleCI

Is CircleCI down?

Short linkrlup.io/down/circleci

I'm having a problem

Operationalchecked 2 minutes ago

We reached CircleCI from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured CircleCI (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:27 AM UTC
US-East120 msOperational
US-West264 msOperational
Europe269 msOperational
Asia-Pacific230 msOperational
their status pagetheir claim, not our reading

CircleCI reports: All systems operational (“All Systems Operational”)

from CircleCI's own status page, checked Sep 3, 2026, 12:27 AM UTC
Our probes and CircleCI's own status page agree: both show CircleCI as reachable right now.

CircleCI's own component breakdown, as they publish it

  • Atlassian Bitbucket APIOperational
  • AWSOperational
  • Docker JobsOperational
  • Atlassian Bitbucket Source downloadsOperational
  • Google Cloud Platform Google Cloud DNSOperational
  • Machine JobsOperational
  • Atlassian Bitbucket SSHOperational
  • Google Cloud Platform Google Cloud NetworkingOperational
  • macOS JobsOperational
  • Atlassian Bitbucket WebhooksOperational
  • Google Cloud Platform Google Cloud StorageOperational
  • Windows JobsOperational
  • Docker HubOperational
  • Google Cloud Platform Google Compute EngineOperational
  • Pipelines & WorkflowsOperational
  • CircleCI APIOperational
  • GitHub Git OperationsOperational
  • mailgun APIOperational
  • CircleCI UIOperational
  • GitHub Pull RequestsOperational
  • mailgun Outbound DeliveryOperational
  • ArtifactsOperational
  • GitHub API RequestsOperational
  • mailgun SMTPOperational
  • GitHub PackagesOperational
  • OpenAIOperational
  • RunnerOperational
  • Auth0 User AuthenticationOperational
  • CircleCI WebhooksOperational
  • GitHub WebhooksOperational
  • CircleCI InsightsOperational
  • GitLabOperational
  • CircleCI ReleasesOperational
  • Docker RegistryOperational
  • Docker AuthenticationOperational
  • Notifications & Status UpdatesOperational
  • Anthropic api.anthropic.comOperational
  • Billing & AccountOperational
  • packagecloud.ioOperational

These are CircleCI's components, named and scored by CircleCI. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is CircleCI's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

CircleCI response time, by region

US-East
155msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 391ms2026-08-21 UTC: p95 369ms2026-08-22 UTC: p95 392ms2026-08-23 UTC: p95 368ms2026-08-24 UTC: p95 363ms2026-08-25 UTC: p95 408ms2026-08-26 UTC: p95 177ms2026-08-27 UTC: p95 183ms2026-08-28 UTC: p95 525ms2026-08-29 UTC: p95 515ms2026-08-30 UTC: p95 493ms2026-08-31 UTC: p95 546ms2026-09-01 UTC: p95 541ms2026-09-02 UTC: p95 596ms2026-09-03 UTC: p95 155ms
Aug 5Aug 19Sep 3
US-West
256msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 543ms2026-08-21 UTC: p95 430ms2026-08-22 UTC: p95 215ms2026-08-23 UTC: p95 442ms2026-08-24 UTC: p95 321ms2026-08-25 UTC: p95 374ms2026-08-26 UTC: p95 202ms2026-08-27 UTC: p95 462ms2026-08-28 UTC: p95 908ms2026-08-29 UTC: p95 423ms2026-08-30 UTC: p95 584ms2026-08-31 UTC: p95 739ms2026-09-01 UTC: p95 595ms2026-09-02 UTC: p95 585ms2026-09-03 UTC: p95 256ms
Aug 5Aug 19Sep 3
Europe
141msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 206ms2026-08-21 UTC: p95 282ms2026-08-22 UTC: p95 282ms2026-08-23 UTC: p95 366ms2026-08-24 UTC: p95 428ms2026-08-25 UTC: p95 477ms2026-08-26 UTC: p95 512ms2026-08-27 UTC: p95 672ms2026-08-28 UTC: p95 436ms2026-08-29 UTC: p95 338ms2026-08-30 UTC: p95 314ms2026-08-31 UTC: p95 371ms2026-09-01 UTC: p95 385ms2026-09-02 UTC: p95 435ms2026-09-03 UTC: p95 141ms
Aug 5Aug 19Sep 3
Asia-Pacific
538msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 456ms2026-08-21 UTC: p95 587ms2026-08-22 UTC: p95 706ms2026-08-23 UTC: p95 869ms2026-08-24 UTC: p95 816ms2026-08-25 UTC: p95 869ms2026-08-26 UTC: p95 557ms2026-08-27 UTC: p95 659ms2026-08-28 UTC: p95 689ms2026-08-29 UTC: p95 752ms2026-08-30 UTC: p95 631ms2026-08-31 UTC: p95 802ms2026-09-01 UTC: p95 826ms2026-09-02 UTC: p95 742ms2026-09-03 UTC: p95 538ms
Aug 5Aug 19Sep 3

Is it CircleCI, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not CircleCI -- it cannot diagnose CircleCI's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 120msstatus code: 401checked: Sep 3, 2026, 12:51 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach CircleCI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 264msstatus code: 401checked: Sep 3, 2026, 12:53 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach CircleCI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 269msstatus code: 401checked: Sep 3, 2026, 1:27 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach CircleCI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 230msstatus code: 401checked: Sep 3, 2026, 1:03 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach CircleCI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionCircleCI is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using CircleCI, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for CircleCI yet, which is not evidence that nothing is wrong.

Recent outages

Intermittent errors when viewing plan usage UIs or calling plan usage APIs, 27mdeclared on their status page2026-08-26
GitHub Login Disruption, 1mdeclared on their status page2026-08-25
Insight data is currently delayed, 31mdeclared on their status page2026-08-17
GitHub Incidents impacting CircleCI functionality, 5h 1mdeclared on their status page2026-08-17
Delays starting jobs following planned maintenance, 3h 1mdeclared on their status page2026-08-15
GitHub service degradation may impact customers using GitHub, 10mdeclared on their status page2026-08-12
Delayed pipeline updates and pipeline processing failures, 17mdeclared on their status page2026-08-11
Usage API data delayed for 8/5, 6h 48mdeclared on their status page2026-08-06

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring CircleCI since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for CircleCI covering any window you pick, with our measurements and CircleCI's own claim at the time, side by side.

Full availability history for CircleCI: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching CircleCI, and again when they can reach it again. That is our own measurement from ten regions, not CircleCI's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

CircleCI uptime measured by RealUptimeLive, from this page's own readings.
[![CircleCI uptime measured by RealUptime](https://realuptime.io/outages/circleci/badge.svg?days=30)](https://realuptime.io/outages/circleci)
<a href="https://realuptime.io/outages/circleci"><img src="https://realuptime.io/outages/circleci/badge.svg?days=30" alt="CircleCI uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What CircleCI's SLA implies, from our measurement

At or above your target

We measured none of downtime for CircleCI over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from CircleCI's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://circleci.com/api/v2/me
secondary
https://status.circleci.com/
RealUptime is not affiliated with CircleCI; the name identifies what we measured, and nothing here speaks for CircleCI's own team. We send a single web request to CircleCI from 4 regions on our own schedule and time the response. We do not see inside CircleCI's systems, do not use an account or real transaction, and are not the same signal CircleCI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for CircleCI is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. CircleCI operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)