CircleCI logo

Is CircleCI Down?

Developer ToolsLive status, outages, and incident history

No. CircleCI is up right now.

Every monitored CircleCI system is operational as of August 24, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s
How we know: the official CircleCI status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

CircleCI Component Status

The main CircleCI systems on this page. All 39 are operational right now.

39operational
Artifacts
Operational
Billing & Account
Operational
CircleCI API
Operational

36 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking CircleCI Dependencies » Auth0 User Authentication, CircleCI Dependencies » AWS, CircleCI Dependencies » Google Cloud Platform Google Cloud DNS, CircleCI Dependencies » Google Cloud Platform Google Cloud Networking, CircleCI Dependencies » Google Cloud Platform Google Cloud Storage, CircleCI Dependencies » Google Cloud Platform Google Compute Engine, CircleCI Dependencies » mailgun API, CircleCI Dependencies » mailgun Outbound Delivery, CircleCI Dependencies » mailgun SMTP, CircleCI Dependencies » OpenAI, CircleCI Insights, CircleCI Releases, and 24 more.

Create a free account

Component statuses may change independently during partial outages.

Recent CircleCI Outages & Incidents

Incident history from the official CircleCI status page, including resolution updates.

Insight data is currently delayedResolved Aug 17, 2026 · 30 minResolved

Insights data is good once more. Thank you for your patience. --- [2026-08-17T21:36:07.654Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-17T21:06:09.852Z] (identified) The cause of the issue has been identified and we are at work fixing it.

GitHub Incidents impacting CircleCI functionalityResolved Aug 17, 2026 · 5h 1mResolved

GitHub's APIs appear to be operating normally. --- [2026-08-17T17:23:06.238Z] (monitoring) Some of GitHub's APIs are still degraded, resulting in a small number of failures relating to commit status updates and hook processing. We will continue to do our best to mitigate these effects. --- [2026-08-17T17:01:08.219Z] (monitoring) GitHub API error rates and latencies appear to have recovered. We will continue to monitor. --- [2026-08-17T16:22:24.867Z] (monitoring) We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover. --- [2026-08-17T15:49:39.558Z] (identified) We are continuing to see high error rates on GitHub's APIs and reduced webhook traffic. Customers using GitHub as their VCS may experience impact to their CircleCI platform experience as a result. This is directly linked to the incident GitHub is experiencing: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We will provide updates as more information becomes available. --- [2026-08-17T14:25:29.256Z] (identified) We are continuing to see high error rates on GitHub APIs and reduced webhook traffic. We will continue to provide updates as more information becomes available. --- [2026-08-17T14:04:21.278Z] (identified) GitHub has reported an incident that is impacting CircleCI pipeline triggering and logging in: https://www.githubstatus.com/incidents/zkxwbgr0cnmx Jobs that are in flights are running, but status reporting to GitHub Pull Requests may fail.

Delays starting jobs following planned maintenanceResolved Aug 15, 2026 · 3h 1mResolved

Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced. Some customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC. This has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.

CircleCI Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a CircleCI incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
May 2688.66% average · 63 days with incidentsAug 24

Going further back: CircleCI uptime by month and every recorded CircleCI outage.

Live CircleCI Outage Reports

Problems reported by engineers using CircleCI. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No CircleCI problems reported yet.

Something wrong with CircleCI on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About CircleCI

CircleCI is a continuous integration and continuous deployment (CI/CD) platform running over one million builds per day for engineering teams. CircleCI outages stall software delivery pipelines. Track CircleCI status and outages here.

Over the past 30 days, PulsAPI has measured CircleCI uptime at 99.86%. Response times, incident history, and SLA tracking for CircleCI are available on the PulsAPI dashboard.

CircleCI Status FAQ

Is CircleCI down right now?

PulsAPI checks CircleCI every 60 seconds. The verdict at the top of this page comes from the latest poll of the official CircleCI status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if CircleCI is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until CircleCI recovers.

How do I check CircleCI uptime history?

PulsAPI tracks CircleCI uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.86%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for CircleCI.

How fast does PulsAPI detect CircleCI outages?

PulsAPI polls the official CircleCI status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual CircleCI components?

Yes. PulsAPI monitors 39 individual CircleCI components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when CircleCI goes down?

Yes. Create a PulsAPI account and subscribe to CircleCI. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever CircleCI status changes.

How do I report an issue with CircleCI to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot CircleCI problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor CircleCI?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor CircleCI alongside up to 24 other services at pulsapi.com/signup.

Track CircleCI with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when CircleCI status changes.

Start free trial