Vendor record
CircleCI
Checked
Front door check counts and CircleCI’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented CircleCI endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- circleci.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every CircleCI product, region or your app worked.
How we count front door checksCircleCI says
Incident posts from CircleCI’s status page, with its titles, impact levels and times. They say what CircleCI chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
10
incidents CircleCI posted, last 30 days
Median recorded duration: 1h 32m. From 10 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Delays starting macOS jobs that use Xcode 26.6.0
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 22m)
Delay in data appearing in UI and API
MajorCircleCI’s postStarted, per CircleCI
Closed in our record(14h 37m)
Elevated wait times for machine jobs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(3h 39m)
Increased task wait times for Docker Gen2
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 15m)
Elevated level of infra fails on customer jobs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 32m)
15 older records
Delay on starting Machine Job Tasks
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(30m)
Delays in pipelines, workflows, UI data, and notifications
MajorCircleCI’s postStarted, per CircleCI
Closed in our record(5h 24m)
Delays starting Gen 2 Docker Jobs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 48m)
Delays in processing new signups and plan changes
Not specifiedCircleCI’s postStarted, per CircleCI
Closed in our record(1h 56m)
Delays starting Linux Machine jobs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(57m)
Customers may experience delays in UI updates
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(4h 44m)
Customers may experience delays in UI updates
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(2h 27m)
Increased wait times for macOS jobs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 1m)
macOS Job Delays
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(1h 44m)
Intermittent errors when viewing plan usage UIs or calling plan usage APIs
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(26m)
Insight data is currently delayed
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(34m)
GitHub Incidents impacting CircleCI functionality
MajorCircleCI’s postStarted, per CircleCI
Closed in our record(5h 5m)
GitHub service degradation may impact customers using GitHub
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(9m)
Usage API data delayed for 8/5
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(6h 54m)
Insights service data is lagging
MinorCircleCI’s postStarted, per CircleCI
Closed in our record(4h 12m)
Your code, your dependencies
See which of your code paths call CircleCI
Connect GitHub or GitLab to find where your public or private repository uses CircleCI. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add CircleCI status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is CircleCI currently down?
CircleCI's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did CircleCI last have an outage?
The most recent closed incident record began 2 days ago and spans 1h 22m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for CircleCI?
No. CheckUpstream checks CircleCI’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor CircleCI in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track CircleCI?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.