Is CircleCI down?
No, CircleCI is not down.
CircleCI’s status page reports no incidents, circleci.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.circleci.com
- Reachable6 of 6 regionsCircleCI API · circleci.com
- Reports in the last hour0Normal
CircleCI’s status page
From status.circleci.com. Read at
- AWS CircleCI DependenciesOperational
- Atlassian Bitbucket API Upstream ServicesOperational
- Docker JobsOperational
- Atlassian Bitbucket Source downloads Upstream ServicesOperational
- Google Cloud Platform Google Cloud DNS CircleCI DependenciesOperational
- Machine JobsOperational
- Atlassian Bitbucket SSH Upstream ServicesOperational
- macOS JobsOperational
Show all 39 components
- Google Cloud Platform Google Cloud Networking CircleCI DependenciesOperational
- Atlassian Bitbucket Webhooks Upstream ServicesOperational
- Google Cloud Platform Google Cloud Storage CircleCI DependenciesOperational
- Windows JobsOperational
- Google Cloud Platform Google Compute Engine CircleCI DependenciesOperational
- Pipelines & WorkflowsOperational
- Docker Hub Upstream ServicesOperational
- mailgun API CircleCI DependenciesOperational
- GitHub Git Operations Upstream ServicesOperational
- CircleCI APIOperational
- CircleCI UIOperational
- mailgun Outbound Delivery CircleCI DependenciesOperational
- GitHub Pull Requests Upstream ServicesOperational
- ArtifactsOperational
- GitHub API Requests Upstream ServicesOperational
- mailgun SMTP CircleCI DependenciesOperational
- GitHub Packages Upstream ServicesOperational
- RunnerOperational
- OpenAI CircleCI DependenciesOperational
- GitHub Webhooks Upstream ServicesOperational
- CircleCI WebhooksOperational
- Auth0 User Authentication CircleCI DependenciesOperational
- CircleCI InsightsOperational
- GitLab Upstream ServicesOperational
- Docker Registry Upstream ServicesOperational
- CircleCI ReleasesOperational
- Notifications & Status UpdatesOperational
- Docker Authentication Upstream ServicesOperational
- Billing & AccountOperational
- Anthropic api.anthropic.com Upstream ServicesOperational
- packagecloud.io Upstream ServicesOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 139 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (circleci.com)
By region
| Region | CircleCI API circleci.com |
|---|---|
| N. Virginia us-east-1 | 401 · 17 ms |
| Oregon us-west-2 | 401 · 103 ms |
| Frankfurt eu-central-1 | 401 · 107 ms |
| Singapore ap-southeast-1 | 401 · 243 ms |
| Tokyo ap-northeast-1 | 401 · 179 ms |
| São Paulo sa-east-1 | 401 · 142 ms |
Two regions check CircleCI every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked CircleCI ourselves since Oct 28, 2026. Earlier days come from its status page.
25 days with problems in the last 90 days.
Recent incidents
Incidents: 10 in the last 30 days and 27 in the last 90, lasting a median of 1 h 39 min.
- Increased Docker gen2 wait timesDegraded1 h 23 min
- Increased wait times for macOS jobs on m4pro.largeDegraded2 h 15 min
- Delays starting macOS jobs that use Xcode 26.6.0Degraded1 h 13 min
- Delay in data appearing in UI and APIPartial outage14 h 35 min
- Elevated wait times for machine jobsDegraded3 h 35 min
- Increased task wait times for Docker Gen2Degraded1 h 10 min
- Elevated level of infra fails on customer jobsDegraded53 min
- Delay on starting Machine Job TasksDegraded26 min
- Delays in pipelines, workflows, UI data, and notificationsPartial outage5 h 18 min
- Delays starting Gen 2 Docker JobsDegraded1 h 39 min
If CircleCI isn’t working for you
CircleCI is a continuous integration and delivery service that runs build, test and deploy pipelines in the cloud or on your own runners.
Common CircleCI errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Too long with no output (exceeded 10m0s): context deadline exceeded | A step printed nothing for 10 minutes, so CircleCI stopped it. | Your side | Add output to long steps or raise no_output_timeout for that step. Source |
Context deadline exceeded after 1 hour - Build timed out (Free tier only) | The job hit the maximum run time for a free plan. | Your side | Speed up or split the job, or upgrade the plan. Source |
Received "killed" signal | The job ran out of memory (often exit code 137) and was killed. | Your side | Use a larger resource class or reduce memory use. Source |
Is it just you?
- Check status.circleci.com for incidents in job starts, specific executors or the UI.
- If jobs stay queued, check your plan's concurrency and any self-hosted runners.
- Read the step output: timeouts and killed signals are about your job, not CircleCI.
- Rerun the job with SSH to inspect the environment if the failure is not obvious.
Alternatives to CircleCI
Questions
Jobs wait when you hit your plan's concurrency, when self-hosted runners are busy or offline, or during a CircleCI incident. Check status.circleci.com and your concurrency settings.
Errors such as Too long with no output usually come from the job itself. If jobs across all projects stay queued or fail to start, check CircleCI's status page and the reports on this page.
Sources: support.circleci.com, support.circleci.com, status.circleci.com
Get alerted when CircleCI breaks your app.
If your product or your team depends on CircleCI, its outage is your outage, and your users will blame you, not CircleCI. Point a Site Qwality monitor at the CircleCI endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.